[perl #44645] [PATCH] [NEW] Refactor configuration options processing

pjcj reported a 403 error on that link. I am regenerating the coverage and it should become available in a few minutes. Sorry for any confusion. kid51 Update: I'll have to fix this later today.

Re: `warn_unused_result' warnings

On Tue, 14 Aug 2007, Andy Lester wrote: On Aug 14, 2007, at 6:27 PM, Andy Dougherty wrote: see above. It would have been nice if gcc simply rejected the attribute so that testing the exit status of gcc would be sufficient. gcc-3.4 doesn't have this problem. The test could either be

[perl #44645] [PATCH] [NEW] Refactor configuration options processing

As this patch has been developed in the reconfigure/ branch, all but one configuration- related package in lib/Parrot/Configure/* has been pushed to 100% statement coverage (see http://thenceforward.net/parrot/coverage/ configure-build/coverage.html). pjcj reported a 403 error on

Need JIT help please - JIT broken with optimized build on Windows (VC)

Hi, JIT is currently broken on x86 Windows using optimized Visual C++ builds. Here's the reason why. Hopefully someone more familiar with the JIT can pick this up. ... 04e45c9a 68f06fe604 push4E66FF0h 04e45c9f e8370a1c0b call_Parrot_set_returns_pc 04e45ca4 83c404 add

[perl #44663] [CAGE] Change Test::* Namespaces to Use Keys

# New Ticket Created by chromatic # Please include the string: [perl #44663] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44663 The Test::More namespace uses 'Test::More' instead of [ 'Test'; 'More' ]. I prefer

Re: Need JIT help please - JIT broken with optimized build on Windows (VC)

Am Mittwoch, 15. August 2007 20:05 schrieb Ron Blaschke: Visual C++ seems to optimize quite heavily, and it looks like it reuses the memory on the stack where arguments are passed for local variables. mov     dword ptr [ebp+0Ch],edx All I know about intel calling convs would summarize this as

Re: Need JIT help please - JIT broken with optimized build on Windows (VC)

Am Mittwoch, 15. August 2007 20:05 schrieb Ron Blaschke: As you can see, the code is heavily optimized.  The pointer to the interpreter is kept on the stack as it should stay the same, only the opcode is exchanged.  *should* is the key word here. Well, another note. This optimization reaches

Re: [perl #44663] [CAGE] Change Test::* Namespaces to Use Keys

Hi, I'm new to the list. I'm a Perl Programmer doing web development in my day job and I'd like to help. I'll try to commit an hour or two per day to parrot project. Can you let me know what I should do to get this done? I mean, do you mean I need to change 'lib/Test/More.pm' or

Re: Need JIT help please - JIT broken with optimized build on Windows (VC)

On 8/15/07, Leopold Toetsch [EMAIL PROTECTED] wrote: This optimization reaches likely back to times, when the opcode engine was designed. It's saving one interpreter push statement [1] per JIT calling one external function, and I've always thought of it as a very cool (and valid) thingy, when

Re: [perl #44663] [CAGE] Change Test::* Namespaces to Use Keys

On Wednesday 15 August 2007 13:42:39 Badai Aqrandista wrote: Hi Badai, I'm new to the list. I'm a Perl Programmer doing web development in my day job and I'd like to help. I'll try to commit an hour or two per day to parrot project. Welcome! Can you let me know what I should do to get this

Re: Need JIT help please - JIT broken with optimized build on Windows (VC)

Leopold Toetsch wrote: Am Mittwoch, 15. August 2007 20:05 schrieb Ron Blaschke: Visual C++ seems to optimize quite heavily, and it looks like it reuses the memory on the stack where arguments are passed for local variables. mov dword ptr [ebp+0Ch],edx All I know about intel calling

Re: [perl #44663] [CAGE] Change Test::* Namespaces to Use Keys

Hi chromatic, Thanks for your prompt reply. The main change is to change all instances of [ 'Test::More' ] and the like to [ 'Test'; 'More' ]. Can you point to a document or a thread that explains about why this change needs to happen? I'm at work now. I'll work on it tonight. -- Thanks,

[perl #44645] [PATCH] [NEW] Refactor configuration options processing

Link has been fixed. You can see coverage analysis for configuration and build tools in reconfigure/ branch at: http://thenceforward.net/parrot/coverage/configure-build/coverage.html After this patch is applied, a similarly high degree of test coverage of config and build tools will prevail in

[perl #44675] [PATCH] t/compilers/pge Change .Class to 'Class'

# New Ticket Created by Colin Kuskie # Please include the string: [perl #44675] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44675 Change .Class to 'Class' in t/compilers/pge Index:

[perl #44683] [PATCH] t/library Change .Class to 'Class'

# New Ticket Created by Colin Kuskie # Please include the string: [perl #44683] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44683 In t/library/*.t, change .Class to the newer 'Class' Index:

[perl #44685] [PATCH] t/oo Change .Class to 'Class'

# New Ticket Created by Colin Kuskie # Please include the string: [perl #44685] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44685 In t/oo/*.t, change .Class to 'Class' Index: t/oo/mro-c3.t

[perl #44681] [PATCH] t/examples Change .Class to 'Class'

# New Ticket Created by Colin Kuskie # Please include the string: [perl #44681] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44681 Change t/examples/streams.t to change .Class to 'Class'. Note, this also required

[perl #44673] [PATCH] t/compilers/json Change .Class to 'Class'

# New Ticket Created by Colin Kuskie # Please include the string: [perl #44673] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44673 This patch changes the old deprecated .Class to 'Class' for t/compilers/json

[perl #44677] [PATCH] t/compilers/tge Change .Class to 'Class'

# New Ticket Created by Colin Kuskie # Please include the string: [perl #44677] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44677 Change .Class to 'Class' in t/compilers/tge Index:

[perl #44657] Re: [CAGE] Finish this module: Parrot::YetToBeNamed!

# New Ticket Created by [EMAIL PROTECTED] # Please include the string: [perl #44657] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44657 I was pondering a suitable value for YetToBeNamed when the thought occurred

[perl #44671] [PATCH] t/compilers/imcc Change .Class to 'Class'

# New Ticket Created by Colin Kuskie # Please include the string: [perl #44671] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=44671 The attached patch changes the deprecated .Class syntax to the more modern

Re: [perl #44687] [PATCH] t/op Change .Class to 'Class'

On Wednesday 15 August 2007 16:30:39 Colin Kuskie wrote: Change all instances of .Class to 'Class' in t/op/*.t Also, I found a new form that may have been missed in earlier patches. I ack'ed for these: ack --perl -l '=\s+new\s+\.\w+' ./t which misses the form: new $P0, .Class Thanks,