From vlad_dumitrescu@REDACTED Fri Jun 3 09:23:29 2005 From: vlad_dumitrescu@REDACTED (Vlad Dumitrescu) Date: Fri, 03 Jun 2005 09:23:29 +0200 Subject: Edoc bug Message-ID: Hi, I noticed that if I use the @hidden tag without any test after it, it isn't recognized by edoc. Adding a space after it make it work, but it's easy to forget :-) I believe the cause is to be found in edoc_tags:scan_tag_2, where there should also be a scan_tag_2([$\r | Cs], Ss, L, As, T) -> scan_tag_lines(Ss, T, [Cs], L + 1, As); clause, allowing for files with Windows line endings. best regards, Vlad _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ From richardc@REDACTED Fri Jun 3 10:26:37 2005 From: richardc@REDACTED (Richard Carlsson) Date: Fri, 03 Jun 2005 10:26:37 +0200 Subject: Edoc bug In-Reply-To: References: Message-ID: <42A0143D.80702@csd.uu.se> Vlad Dumitrescu wrote: > I noticed that if I use the @hidden tag without any test after it, it > isn't recognized by edoc. Adding a space after it make it work, but it's > easy to forget :-) > > I believe the cause is to be found in edoc_tags:scan_tag_2, where there > should also be a > scan_tag_2([$\r | Cs], Ss, L, As, T) -> > scan_tag_lines(Ss, T, [Cs], L + 1, As); > clause, allowing for files with Windows line endings. > > best regards, > Vlad (I forgot to cc the list in my initial reply to Vlad.) Thanks for the report; I obviously never thought for a second of Windows line breaks (can't they be universally banned or something?) when I wrote edoc, so I should have a closer look at all the scanning code. /Richard From serge@REDACTED Thu Jun 16 18:38:17 2005 From: serge@REDACTED (Serge Aleynikov) Date: Thu, 16 Jun 2005 12:38:17 -0400 Subject: snmp release build Message-ID: <42B1AAF9.1050509@hq.idt.net> Hi, When I include an SNMP applicaiton in a release under R10B-5, I am getting a bunch of compilation warnings: proxy.rel: {release, {"proxy","1.0"}, {erts, "100.100.100"}, [{kernel,"2.10.7"}, {stdlib,"1.13.7"}, {snmp, "4.1.4"}, {proxy, "1.0"}]}. >erlc -pa ../ebin -o ../ebin -d proxy.rel *WARNING* snmp: Source code not found: snmp.erl *WARNING* snmp: Source code not found: snmp_app.erl *WARNING* snmp: Source code not found: snmp_app_sup.erl *WARNING* snmp: Source code not found: snmpa.erl *WARNING* snmp: Source code not found: snmpa_acm.erl *WARNING* snmp: Source code not found: snmpa_agent.erl *WARNING* snmp: Source code not found: snmpa_agent_sup.erl *WARNING* snmp: Source code not found: snmpa_app.erl *WARNING* snmp: Source code not found: snmpa_authentication_service.erl *WARNING* snmp: Source code not found: snmpa_error.erl *WARNING* snmp: Source code not found: snmpa_error_io.erl *WARNING* snmp: Source code not found: snmpa_error_logger.erl *WARNING* snmp: Source code not found: snmpa_error_report.erl *WARNING* snmp: Source code not found: snmpa_general_db.erl ... I traced this to the systools_make:make_script() that cannot guess the location of SNMP's source files because they haven't been stored using conventional directories: >ls -al /usr/local/lib/erlang/lib/snmp-4.1.4/src total 28 drwxr-xr-x 7 root root 4096 Jun 15 16:10 . drwxr-xr-x 9 serge devlp 4096 Jun 15 16:10 .. drwxr-xr-x 2 root root 4096 Jun 15 16:10 agent drwxr-xr-x 2 root root 4096 Jun 15 16:10 app drwxr-xr-x 2 root root 4096 Jun 15 16:10 compiler drwxr-xr-x 2 root root 4096 Jun 15 16:10 manager drwxr-xr-x 2 root root 4096 Jun 15 16:10 misc I think it can be considered a bug in the SNMP. I don't see a good way of hiding these warning messages ("+silent" option given to erlc doesn't quite help). Serge From ft@REDACTED Fri Jun 17 11:28:09 2005 From: ft@REDACTED (Fredrik Thulin) Date: Fri, 17 Jun 2005 11:28:09 +0200 Subject: compiler bug in R10B-5 Message-ID: <200506171128.09542.ft@it.su.se> Hi A friend of mine found this to me unexplainable compiler bug. It would be interesting to hear a few words about the cause, besides getting it fixed ;) $ /pkg/erlang/R10B-5/bin/erlc bug.erl Function pstnproxy_add_headers/2 refers to undefined label 6 ./bug.erl:none: internal error in beam_clean; crash reason: {{case_clause,{'EXIT',{undefined_label,6}}}, [{compile,'-select_passes/2-anonymous-2-',2}, {compile,'-internal_comp/4-anonymous-1-',2}, {compile,fold_comp,3}, {compile,internal_comp,4}, {compile,internal,3}]} $ Trevlig helg / have a nice weekend /Fredrik -------------- next part -------------- -module(bug). -export([pstnproxy_add_headers/2]). -record(request, { header }). -record(siporigin, { proto }). pstnproxy_add_headers(Request, Origin) when is_record(Request, request), is_record(Origin, siporigin) -> NewHeaders1 = Request#request.header, NewHeaders2 = case (Origin#siporigin.proto == tls) or (Origin#siporigin.proto == tls6) of true -> keylist:delete("X-Foo2", NewHeaders1); false -> keylist:delete("X-Foo2", NewHeaders1) end, NewHeaders3 = case (Origin#siporigin.proto == tls) or (Origin#siporigin.proto == tls6) of true -> keylist:delete("X-Foo3", NewHeaders2); false -> keylist:delete("X-Foo3", NewHeaders2) end, Request#request{header = NewHeaders3}.