Re: rx.ops, bitmaps and memory leaks

2002-11-08 Thread Leopold Toetsch
Brent Dax wrote: > Leopold Toetsch: > # 2) For bitmaps I would provide a bitlist.c with functions for setting > # and testing bits. This bitlist would be based on list, so it > # should be > # fast enough and had no limits WRT unicode chars. > > Note that the "Bitmaps" used by rx are only bitmaps

RE: rx.ops, bitmaps and memory leaks

2002-11-08 Thread Brent Dax
Leopold Toetsch: # 2) For bitmaps I would provide a bitlist.c with functions for setting # and testing bits. This bitlist would be based on list, so it # should be # fast enough and had no limits WRT unicode chars. Note that the "Bitmaps" used by rx are only bitmaps within US-ASCII, to keep siz

Re: [perl #18219] on_exit not portable

2002-11-08 Thread Josh Wilmes
At 8:02 on 11/08/2002 +0100, Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Josh Wilmes wrote: > > > For the meantime, I have added the Parrot_exit and Parrot_on_exit function s > > to CVS. > > Thanks for providing this. I did slightly modify your patch to really > get rid of the leaks: > - test

rx.ops, bitmaps and memory leaks

2002-11-08 Thread Leopold Toetsch
Rx had some time ago (~0.0.6) a state structure rxinfo. AFAIK this was tossed for speed reasons, state is kept in registers now. This has several impacts: - regexen are not reentrant anymore (global intstack) - they don't/can't manage their allocated resources like bitmaps 1) I would propose, tha

Re: [perl #18189] Test failures with 'long long' on i386/linux

2002-11-08 Thread Leopold Toetsch
Andy Dougherty (via RT) wrote: # New Ticket Created by Andy Dougherty # Please include the string: [perl #18189] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt2/Ticket/Display.html?id=18189 > Not OK: This is a failure report for parrot. When bu