Re: More perl5.005 problems

2004-07-08 Thread Michael G Schwern
On Mon, Jun 14, 2004 at 05:26:14PM -0400, Dan Sugalski wrote: > At 4:39 PM -0400 6/14/04, Michael G Schwern wrote: > >On Mon, Jun 14, 2004 at 12:00:42PM -0400, Andy Dougherty wrote: > >> For some reason I haven't been able to figure out, perl5.00503 can't seem > >> to handle the TODO test in t/pmc/

Re: More perl5.005 problems

2004-07-08 Thread Michael G Schwern
On Mon, Jun 14, 2004 at 02:49:35PM -0700, chromatic wrote: > In fact, I'm surprised he managed to install an acceptably recent > version of Test::Simple on 5.5.3 without upgrading Test::Harness; the > bundle's required Test::Harness 2.03 for a couple of years now. Parrot ships with Test::Simple/Mo

bad free()s in string.t

2004-07-08 Thread Nicholas Clark
If I build parrot with --gc=libc on OS X I see some warnings about bad pointers being passed to free(). It's happening in a call from dod.c: #ifdef GC_IS_MALLOC /* free allocated space at (int*)bufstart - 1, * but not if it is used COW or external

Python::Bytecode

2004-07-08 Thread Leopold Toetsch
... is on CPAN (said Dan) and is broken. I'd be glad if people could fix it and send me a running version ;) * constants are messed up * it doesn't disassemble all code objects of a .pbc - just one $ cd languages/python $ perl pie-thon.pl -dD some.py shows more (and AFAIK correct) Python disassem

Re: bad free()s in string.t

2004-07-08 Thread Leopold Toetsch
Nicholas Clark wrote: If I build parrot with --gc=libc on OS X I see some warnings about bad pointers being passed to free(). It's happening in a call from dod.c: #ifdef GC_IS_MALLOC /* free allocated space at (int*)bufstart - 1, * but not if it is used COW