Re: [perl #36882] [BUG] PGE globber, empty strings

2005-08-12 Thread Will Coleda
Updating Data::Escape seems like a better option to me. On Aug 12, 2005, at 3:12 PM, Patrick R. Michaud wrote: On Fri, Aug 12, 2005 at 11:37:53AM -0700, Will Coleda wrote: # New Ticket Created by Will Coleda # Please include the string: [perl #36882] # in the subject line of all future corr

Re: [perl #36882] [BUG] PGE globber, empty strings

2005-08-12 Thread Patrick R. Michaud
On Fri, Aug 12, 2005 at 11:37:53AM -0700, Will Coleda wrote: > # New Ticket Created by Will Coleda > # Please include the string: [perl #36882] > # in the subject line of all future correspondence about this issue. > # https://rt.perl.org/rt3/Ticket/Display.html?id=36882 > > > > Trying to glo

[perl #36884] [TODO] teardown parrot cvs repo

2005-08-12 Thread via RT
# New Ticket Created by jerry gay # Please include the string: [perl #36884] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=36884 > since parrot has migrated from cvs to svn, and there's little chance it'll migrate back, t

[perl #36882] [BUG] PGE globber, empty strings

2005-08-12 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #36882] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=36882 > Trying to glob empty strings causes a bus error. I would expect this to be a match. wo

Re: [perl #36812] Compiling Pugs against Parrot

2005-08-12 Thread Adrian Lambeck
> Strange. You could replace the .IGLOBALS_CONFIG_HASH with it's value (6) > (and drop the .include line) and try to track down what's wrong with: > > $ bin/parrot parrot-config.imc prefix I did that - and the same with line 56 concerning iterator.pasm because that also did not work. Afterwards i

Re: [perl #36862] [RESOLVED] [PATCH] m4 tests compatible with Win32

2005-08-12 Thread Francois PERRAD
At 10:42 11/08/2005 -0700, you wrote: According to our records, your request regarding "[PATCH] m4 tests compatible with Win32" has been resolved. the patch wasn't correctly applied. the test fails on Win32 : # Failed test (m4\t\builtins\010_sysval.t at line 26) # got: ''$true'