[perl #42339] [CAGE] Test Valid and Invalid Parrot Flags

2007-04-08 Thread via RT
# New Ticket Created by chromatic # Please include the string: [perl #42339] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42339 When Parrot processes its command-line arguments, it detects valid and invalid flags

request for a few Pugs parser updates

2007-04-08 Thread Darren Duncan
Hello, This note is a request for help from anyone that is saavy with the Pugs internals such that they can add a few small features, to the parser mainly, without too much difficulty. While trying to port a significant codebase (ext/QDRDBMS/) to Perl 6 from Perl 5, I discovered that a few

[perl #42336] segfault happens with 'parrot --pre-process-only'

2007-04-08 Thread Jim McKim
# New Ticket Created by Jim McKim # Please include the string: [perl #42336] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42336 --- osname= linux osvers= 2.6.15-gentoo-alt2 arch= x86_64-linux cc=

[perl #42339] [CAGE] Test Valid and Invalid Parrot Flags

2007-04-08 Thread James Keenan via RT
On Sun Apr 08 00:07:13 2007, [EMAIL PROTECTED] wrote: When Parrot processes its command-line arguments, it detects valid and invalid flags and reports invalid flags, then exits with an exit code of 1. I could find no tests for this feature. They would be lovely to have. A week ago I

[perl #42332] [TODO]: Eliminate t/tools/ops2pmutils/testlib/Capture.pm

2007-04-08 Thread James Keenan via RT
t/tools/ops2pmutils/testlib/Capture.pm was deleted in r18040. All tests using it were modified to use Parrot::IO::Capture::Mini. 'make buildtools_tests' run; all test passed. Closing ticket.

[perl #42349] [TODO] dotnet - fix various ops for 64 bit architectures

2007-04-08 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #42349] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42349 In languages/dotnet/ops/dotnet.ops, the following ops need to be fixed for 64 bit

[perl #42350] [TODO] fix kludge in find_type op

2007-04-08 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #42350] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42350 There is a warning in src/ops/pmc.ops within the find_type() op: KLUDGE ALERT -

[perl #42352] [TODO] fix or remove strange TODO item in hash() op

2007-04-08 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #42352] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42352 In src/ops/pmc.ops within the hash() op, there is a todo item which is just marked

[perl #42353] [TODO] perform a dynamic lookup if needed in pic_infix__() op

2007-04-08 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #42353] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42353 In src/ops/pic.ops at the pic_infix__() op there is the todo item: if we got too

[perl #42354] [TODO] preserve type system in pic_inline_sub__() op

2007-04-08 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #42354] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42354 In the file src/ops/pic.ops in the pic_inline_sub__() op there is the todo item:

[perl #42355] [TODO] use ARG_MAX in pic_callr__() op

2007-04-08 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #42355] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42355 In the file src/ops/pic.ops in the pic_callr__() op there is a todo item which

[perl #42356] [TODO] verify $1 didn't change in pic_callr__() op

2007-04-08 Thread via RT
# New Ticket Created by Paul Cochrane # Please include the string: [perl #42356] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42356 In the file src/ops/pic.ops within the pic_callr__() op, there is the todo item:

Re: [perl #42339] [CAGE] Test Valid and Invalid Parrot Flags

2007-04-08 Thread chromatic
On Sunday 08 April 2007 06:37, James Keenan via RT wrote: On Sun Apr 08 00:07:13 2007, [EMAIL PROTECTED] wrote: When Parrot processes its command-line arguments, it detects valid and invalid flags and reports invalid flags, then exits with an exit code of 1. I could find no tests for

[perl #42359] [PATCH] Assorted cleanups - part III (Intel C++)

2007-04-08 Thread via RT
# New Ticket Created by Steve Peters # Please include the string: [perl #42359] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42359 The attached patch includes several cleanups needed to silence warnings when

[perl #42359] [PATCH] Assorted cleanups - part III (Intel C++)

2007-04-08 Thread Steve Peters via RT
On Sun Apr 08 16:08:05 2007, stmpeters wrote: The attached patch includes several cleanups needed to silence warnings when compiling Parrot with Intel C++. It helps to attach the right patch Steve intel_cleanups.out Description: Binary data

[perl #42360] [TODO]: Unit tests for Parrot::Revision

2007-04-08 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #42360] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42360 lib/Parrot/Revision.pm appears to have no unit tests written specifically for it.

[perl #42362] [TODO]: Unit tests for modules used during configuration

2007-04-08 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #42362] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=42362 Suppose that I run the tests in t/configure/*.t with Devel::Cover: $ cover -delete