Re: November

2008-08-17 Thread Carl Mäsak
Conrad (): Do you plan to make a publicly-usable version of this wiki available, perhaps on the feather development system? Yes, that is our next TODO item. We'll notify the list once something is set up. // Carl

[perl #58034] [TODO] save config_args for make reconfig

2008-08-17 Thread via RT
# New Ticket Created by Reini Urban # Please include the string: [perl #58034] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58034 --- osname= cygwin osvers= 1.5.25(0.15642) arch= cygwin-thread-multi-64int cc=

Re: [perl #57960] Inconsistent for loop semantics

2008-08-17 Thread Carl Mäsak
It was revision 28928 that introduced this difference between the for statement and statement-modifying for. I'm not sure exactly what issue it intended to fix, but if I undo that revision everything works according to my (not necessarily correct) expectations. $ svn log -r28928

[perl #58034] [TODO] save config_args for make reconfig

2008-08-17 Thread James Keenan via RT
Reini, I would argue that we take a different approach with 'make reconfig'. We need to get rid of it entirely. In Parrot years, it's ancient code: $ svn blame config/gen/makefiles/root.in | grep -n -A 3 reconfig ... -- 708: 4916 boemmels @echo reconfig: 'clean' and redo

[perl #58004] Investigate junction of code object failures (S03-junctions/misc.t)

2008-08-17 Thread [EMAIL PROTECTED] (via RT)
# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #58004] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58004 - Likely depends on junction dispatcher

[perl #57970] Finish implementing radix notation (see S02-literals/radix.t for details)

2008-08-17 Thread [EMAIL PROTECTED] (via RT)
# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #57970] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=57970 - C code in Perl6Str.pmc needs refactoring and updating

[perl #57958] [BUG] [PATCH] config/auto/attributes.pm not cleaning up after itself properly

2008-08-17 Thread James Keenan via RT
Since this was a bug, I felt I should move on it before this week's release. In r30279 I applied a modified version of the patch submitted earlier: I added $conf-cc_clean() at one location. I then trimmed the list of configuration steps to end at auto::attributes and reconfigured. An 'ls' on

[perl #58030] Named parameter passing errors on subs with optional parameters

2008-08-17 Thread mhelix
# New Ticket Created by mhelix # Please include the string: [perl #58030] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58030 Passing PMCs as named arguments fails when the called sub accepts optional positional

[PATCH][perl #58030] Bugfix of Named parameter passing errors

2008-08-17 Thread mhelix
The first named parameter isn't set if optional parameters are missing. The function Parrot_process_args didn't save the value of the argument. I used memcpy to copy the UnionVal. If there's a neater way to do that please fix my fix :) . It only adds a couple of lines to src/inter_call.c.

[perl #58036] [BUG] [PATCH] config/auto/warnings.pm not cleaning up after itself properly

2008-08-17 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #58036] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58036 This is the same problem for which I submitted a patch yesterday with respect to

[perl #58036] [BUG] [PATCH] config/auto/warnings.pm not cleaning up after itself properly

2008-08-17 Thread James Keenan via RT
Applied in r30280.

[perl #58014] Implement NaN and Inf

2008-08-17 Thread [EMAIL PROTECTED] (via RT)
# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #58014] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58014 - Need to determine if Parrot will support NaN/Inf directly, or if Rakudo

Re: [perl #58034] [TODO] save config_args for make reconfig

2008-08-17 Thread Reini Urban
James Keenan via RT schrieb: Reini, I would argue that we take a different approach with 'make reconfig'. We need to get rid of it entirely. In Parrot years, it's ancient code: $ svn blame config/gen/makefiles/root.in | grep -n -A 3 reconfig ... -- 708: 4916 boemmels @echo reconfig:

Re: [perl #57668] [BUG][PATCH] Iterate through the current namespace causes a segfault

2008-08-17 Thread chromatic
On Saturday 16 August 2008 15:36:42 Bob Rogers wrote: This test (t/pmc/namespace.t:65) seems to cause an unbounded memory-gobbling loop on my configuration (GNU/Linux/x86). It only happens rarely ( 1 in 35 so far), though it eats my machine when it does . . . I take that back;

codingstd tests should pass in every release

2008-08-17 Thread Bob Rogers
I notice that docs/project/release_manager_guide.pod says (line 123): It is not necessary to quiet all the codingstd tests for a release. Since these tests are on make test (and hence visible to non-developers), and are being tested with Smolder in any case, I think this

Re: codingstd tests should pass in every release

2008-08-17 Thread chromatic
On Sunday 17 August 2008 09:29:14 Bob Rogers wrote: I notice that docs/project/release_manager_guide.pod says (line 123): It is not necessary to quiet all the codingstd tests for a release. Since these tests are on make test (and hence visible to non-developers), and are

Re: codingstd tests should pass in every release

2008-08-17 Thread Bob Rogers
From: chromatic [EMAIL PROTECTED] Date: Sun, 17 Aug 2008 09:39:05 -0700 Not all of the codingstd tests are part of make test. There's a specific codingstd test target you can run separately. I estimate about 2/3 of the tests will pass. The others may or may not ever pass. For

Re: [perl #57668] [BUG][PATCH] Iterate through the current namespace causes a segfault

2008-08-17 Thread Reini Urban
chromatic schrieb: On Saturday 16 August 2008 15:36:42 Bob Rogers wrote: This test (t/pmc/namespace.t:65) seems to cause an unbounded memory-gobbling loop on my configuration (GNU/Linux/x86). It only happens rarely ( 1 in 35 so far), though it eats my machine when it does . . . I

[perl #58040] [BUG] namespace_65.pir hangs with --optimize

2008-08-17 Thread via RT
# New Ticket Created by Reini Urban # Please include the string: [perl #58040] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=58040 --- osname= cygwin osvers= 1.5.25(0.15642) arch= cygwin-thread-multi-64int cc=

Re: [perl #58032] [BUG] languages/perl6/t/pmc/perl6multisub-dispatch-tiebreak.t: filename is too long

2008-08-17 Thread Jonathan Worthington
James Keenan (via RT) wrote: We appear to have a coding standard which limits us to 32 characters in a file's basename. This particular test file has 33 characters. Oh, coding standards tests, how I love thee... (To note why I've not been bothering to run them the last couple of days, they

[svn:parrot-pdd] r30278 - trunk/docs/pdds

2008-08-17 Thread Whiteknight
Author: Whiteknight Date: Sun Aug 17 07:55:32 2008 New Revision: 30278 Modified: trunk/docs/pdds/pdd09_gc.pod Log: [GC] Remove mention of GC_no_trace_volatile_roots from PDD09 and include/parrot/dod.h. The flag is not used anywhere in Parrot, and is not documented well enough to be

make fulltest failures

2008-08-17 Thread Bob Rogers
I ran make fulltest in r30280 and got some test failures, which are summarized below. I will start submitting tickets for these shortly (with the exception of codingstd_tests, which I assume doesn't need it). If you have some cycles to spare, fixing these before the release would be greatly

Re: [perl #57900] solaris hints no longer work

2008-08-17 Thread chromatic
On Wednesday 13 August 2008 15:20:08 Andrew Johnson via RT wrote: Almost, you just missed the executable itself (-o arg). This patch works for me. Thanks, applied as r30282. -- c

RE: November

2008-08-17 Thread Conrad Schneiker
Carl Mäsak wrote: Conrad (): Do you plan to make a publicly-usable version of this wiki available, perhaps on the feather development system? Yes, that is our next TODO item. We'll notify the list once something is set up. Excellent. FYI, I've also referenced your work here (see the

[svn:parrot-pdd] r30284 - in trunk/docs/pdds: . draft

2008-08-17 Thread chromatic
Author: chromatic Date: Sun Aug 17 13:26:18 2008 New Revision: 30284 Modified: trunk/docs/pdds/draft/pdd08_keys.pod trunk/docs/pdds/pdd09_gc.pod trunk/docs/pdds/pdd23_exceptions.pod trunk/docs/pdds/pdd27_multiple_dispatch.pod Log: [PDD] Fixed PDD linewrapping at 78 characters, per

Re: [perl #57668] [BUG][PATCH] Iterate through the current namespace causes a segfault

2008-08-17 Thread chromatic
On Sunday 17 August 2008 09:22:34 chromatic wrote: Ah good, Christoph and I tried to track that down the other day. I'll do my best to fix it, but I may not have reliable network access. If you don't see a patch from me before the release, +1 to SKIP it. Fixed in r30286. -- c

Re: [perl #58040] [BUG] namespace_65.pir hangs with --optimize

2008-08-17 Thread chromatic
On Sunday 17 August 2008 11:16:08 Reini Urban wrote: Without --optimize ./parrot t/pmc/namespace_65.pir works fine. It prints bar 2 With --optimize ./parrot t/pmc/namespace_65.pir hangs after the 2. Attaching the debugger to a non-debug build is too heavy for me now, I'll try to get it

Re: [perl #57668] [BUG][PATCH] Iterate through the current namespace causes a segfault

2008-08-17 Thread Bob Rogers
From: chromatic [EMAIL PROTECTED] Date: Sun, 17 Aug 2008 14:49:50 -0700 On Sunday 17 August 2008 09:22:34 chromatic wrote: Ah good, Christoph and I tried to track that down the other day. I'll do my best to fix it, but I may not have reliable network access. If you don't

Re: codingstd tests should pass in every release

2008-08-17 Thread James E Keenan
Bob Rogers wrote: From: chromatic [EMAIL PROTECTED] Date: Sun, 17 Aug 2008 09:39:05 -0700 Not all of the codingstd tests are part of make test. There's a specific codingstd test target you can run separately. I estimate about 2/3 of the tests will pass. The others may or may

Re: make fulltest failures

2008-08-17 Thread James E Keenan
Bob Rogers wrote: *** gmake manifest_tests Failed Test Stat Wstat Total Fail Failed List of Failed t/manifest/02-regenerate_file.t1 256121 8.33% 5 Failed 1/5 test scripts,

Re: make fulltest failures

2008-08-17 Thread James E Keenan
Bob Rogers wrote: *** gmake codingstd_tests Failed Test Stat Wstat Total Fail Failed List of Failed t/codingstd/c_function_docs.t1 256 11 100.00% 1 t/codingstd/fixme.t

[perl #58032] [BUG] languages/perl6/t/pmc/perl6multisub-dispatch-tiebreak.t: filename is too long

2008-08-17 Thread James Keenan via RT
In r30288, renamed the file by omitting '-dispatch'. Renamed two siblings for consistency. Changed names within these 3 files. Rebuilt. Ran 'prove' on the directory in question. All tests continue to pass. Resolving ticket.

Re: make fulltest failures

2008-08-17 Thread Bob Rogers
From: James E Keenan [EMAIL PROTECTED] Date: Sun, 17 Aug 2008 19:59:54 -0400 Bob Rogers wrote: *** gmake manifest_tests Failed Test Stat Wstat Total Fail Failed List of Failed

[perl #58046]: t/pmc/exception_handler.t should be renamed

2008-08-17 Thread Bob Rogers
Fixed in r30283. -- Bob

Re: codingstd tests should pass in every release

2008-08-17 Thread Bob Rogers
From: James E Keenan [EMAIL PROTECTED] Date: Sun, 17 Aug 2008 19:55:02 -0400 Yes, when one of the 'make codingstd_tests' accumulates sufficient PASSes, we promote it to 'make test'. Those that are not yet passing can generally be described as: Requires cage-cleaner with vast

[perl #57956] [BUG] [PATCH] config/auto/sizes.pm not cleaning up after itself

2008-08-17 Thread James Keenan via RT
On Fri Aug 15 17:36:24 2008, [EMAIL PROTECTED] wrote: Since I have never actually written a probe before, please review this. I can state that on Linux, it results in the same value for $PConfig{hugefloatvalsize} as previously. Consequently, all core tests continue to pass. If