Re: [CVS ci] don't trace system areas in sweep opcode

2003-08-05 Thread Piers Cawley
"Brent Dax" <[EMAIL PROTECTED]> writes: > Leopold Toetsch: >> To clean up on scope exit (and after a Perl C ins), the HL emits >> a C opcode. This doesn't do C anymore, >> because there is nothing unanchored and alive beyond the runloop's stack. > > Have I mentioned lately that you guys are geni

Re: [CVS ci] don't trace system areas in sweep opcode

2003-07-31 Thread Brent Dax
Leopold Toetsch: > To clean up on scope exit (and after a Perl C ins), the HL emits > a C opcode. This doesn't do C anymore, > because there is nothing unanchored and alive beyond the runloop's stack. Have I mentioned lately that you guys are geniuses? --Brent Dax <[EMAIL PROTECTED]> Perl and P

[CVS ci] don't trace system areas in sweep opcode

2003-07-28 Thread Leopold Toetsch
After a thorough discussion at the Parrot BOF at Paris, we got a solution for timely destruction vs trace system areas and bogus objects. To clean up on scope exit (and after a Perl C ins), the HL emits a C opcode. This doesn't do C anymore, because there is nothing unanchored and alive beyond