The R9C2 man page for gen_server:reply/2 claims the
function returns 'true', but it actually returns
something like:
{Tag, Reply} | {'EXIT', Rsn}
Best,
Thomas
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
You currently can't define macros with the same name as keywords: -define(begin, 4711). -define(end, 11147). % compiler complains "badly formed define" However, this restriction is, as far as I can see, unnecessary: the namespaces are entirely distinct. That is, when you subsequently use the macro, it will be written '?begin', which will never be confused with plain 'begin'. Hence, I report this as a bug. Best, Thomas __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail
I understand the reasoning, but from a practical perspective, isn't it
better to stay away from names like that - just to avoid confusion?
(Especially with newbies)
-------
begin
case ?begin of
vs
case ?BEGIN_PORT of
-------
A bit far fetched though :)
On Wed, 2004-09-08 at 16:08, Thomas Lindgren wrote:
> You currently can't define macros with the same name
> as keywords:
>
> -define(begin, 4711).
> -define(end, 11147).
>
> % compiler complains "badly formed define"
>
> However, this restriction is, as far as I can see,
> unnecessary: the namespaces are entirely distinct.
> That is, when you subsequently use the macro, it will
> be written '?begin', which will never be confused with
> plain 'begin'.
>
> Hence, I report this as a bug.
>
(Continue reading)
--- Danie Schutte <danie <at> erlfinsys.net> wrote: > I understand the reasoning, but from a practical > perspective, isn't it > better to stay away from names like that - just to > avoid confusion? > (Especially with newbies) Actually, I thought it a bit confusing that one _couldn't_ define begin, end, etc(Continue reading)Personally, I would consider "[staying] away from names like that" a matter for organizational coding standards, rather than language standards. For instance, you can already use 'begin', 'end' and so on as atoms. And Erlang macros can already be confusing for all the usual reasons (just like C macros). Best, Thomas PS. Nice domain name
Hi!
I just got the following error:
=ERROR REPORT==== 2004-09-11 00:16:25 ===
Mnesia('ejabberd <at> yo.jabber.ru'): ** ERROR ** (core dumped to file: "/opt/jabber/server/ejabberd/src/MnesiaCore.ejabberd <at> yo.jabber.ru_1094_847385_25236")
** FATAL ** mnesia_locker crashed: {badarg,
[{erlang,
'++',
[{error,
{premature_eof,
"/opt/jabber/server/ejabberd/src/Mnesia.ejabberd <at> yo.jabber.ru/roster.DAT"}},
[]]},
{lists,append,2},
{mnesia_locker,
set_read_lock_on_all_keys,
6},
{mnesia_locker,loop,1},
{mnesia_sp,init_proc,4},
{proc_lib,init_p,5}]} state: [<0.87.0>]
After that mnesia have stopped.
I can send that MnesiaCore file (it is less than 300KB).
I've noticed that my "make install" command fails for R9C-2 on my OSX Mac because the /usr/local/lib/erlang/Install script at line 95 does a if [ -d $ERL_ROOT/lib/sasl* ] which fails with [yoghurt:~/erlang/otp_src_R9C-2] reto% sudo make install.Install Password: cd /usr/local/lib/erlang && ./Install -minimal /usr/local/lib/erlang ./Install: line 95: [: too many arguments Formatting manual pages (this may take a while...) make: *** [install.Install] Error 127 It turns out that I've got 3 version of the sasl application installed (back from older OTP releases that I used): /usr/local/lib/erlang/lib/sasl-1.10: /usr/local/lib/erlang/lib/sasl-1.9.3: /usr/local/lib/erlang/lib/sasl-1.9.4: My work around was to patch the line to be if [ -d $ERL_ROOT/lib/sasl-1.10* ] This then allowed the sasl boot script to be generated correctly (it now is the R9 script that includes kernel-2.9 rather than 2.8, which is what I cared about). Best regards,(Continue reading)
In one of my testcases sasl prints information to the terminal that I start the testrun from (I use the batch option, so no new window is opened). I had hoped that sasl output would be captured per testcase like io:formation material is. Is this a bug, or do I have to do something special to capture the sasl reports (ideally associated with the test case that triggered them)? Thanks, - Reto
This is not a big issue, but rather confusing to the newby.
If I start a node with the {cleanup, false} option and later stop it in
another testcase function [**], I receive the warning:
== WARNING: Attempt to stop a nonexisting slavenode (test_a <at> yoghurt)
=== Trying to kill it anyway!!!
This warning is missleading in this context since the node is indeed
running (left running). Perhaps the warning can be avoided by
implicitly pinging the node beforehand?
Thanks,
- Reto
start(Config) when list(Config) ->
?line {ok, test_a <at> yoghurt} =
?t:start_node(
test_a, slave,
[{args, "-pa /Users/reto/sdev/discover/src/discover-1.0/ebin"},
{cleanup, false}]), % keep node alive until stop/1
...
stop(Config) when list(Config) ->
?line pong = net_adm:ping(test_a <at> yoghurt), % still there
% Note that the following warning in the output of stop/1 is
missleading
% since the node is in fact alive.
%
(Continue reading)All of the driver-related functions are not exported from beam.dll, including driver_output. This prevents dynamically loaded drivers from even *loading* under Windows. This is a showstopper for users of Wings, esdl, or any other application making use of custom drivers. I'd like to see a new beam.dll for R9C-2 posted as soon as possible. James
Hmm, they work for me (from the binary distribution)... Maybe it's something with the source build? /Vlad ----- Original Message ----- From: "James Hague" <jamesh <at> Volition-inc.com> To: <erlang-bugs <at> erlang.org> Sent: Tuesday, September 21, 2004 3:22 PM Subject: Missing beam.dll exports in R9C-2 for Windows > All of the driver-related functions are not exported from beam.dll, > including driver_output. This prevents dynamically loaded drivers from > even > *loading* under Windows. > > This is a showstopper for users of Wings, esdl, or any other application > making use of custom drivers. I'd like to see a new beam.dll for R9C-2 > posted as soon as possible. > > James >
RSS Feed22 | |
|---|---|
76 | |
47 | |
45 | |
84 | |
82 | |
41 | |
65 | |
74 | |
44 | |
55 | |
20 | |
43 | |
47 | |
41 | |
41 | |
36 | |
28 | |
34 | |
47 | |
43 | |
29 | |
24 | |
40 | |
58 | |
78 | |
67 | |
73 | |
23 | |
33 | |
38 | |
22 | |
43 | |
68 | |
54 | |
38 | |
54 | |
37 | |
18 | |
40 | |
28 | |
35 | |
46 | |
33 | |
37 | |
53 | |
48 | |
53 | |
79 | |
30 | |
35 | |
32 | |
31 | |
40 | |
35 | |
34 | |
53 | |
58 | |
66 | |
43 | |
43 | |
52 | |
58 | |
42 | |
33 | |
55 | |
61 | |
30 | |
31 | |
53 | |
16 | |
19 | |
19 | |
18 | |
21 | |
6 | |
25 | |
9 | |
23 | |
17 | |
15 | |
14 | |
12 | |
7 | |
11 | |
11 | |
5 | |
13 | |
9 | |
5 | |
10 | |
3 | |
4 | |
10 | |
3 | |
4 | |
4 | |
4 | |
13 | |
16 | |
8 | |
6 | |
4 | |
6 | |
17 | |
3 | |
2 | |
1 | |
4 | |
1 | |
3 | |
5 | |
1 | |
6 | |
1 | |
1 | |
1 |
