Nick~
On 9/15/05, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 15, 2005 at 01:13:17PM -0400, Matt Fowles wrote:
> > Nick~
> >
> > Dan's plan was to do a topographic sort of the object tree to avoid
> > this problem for non-loops and to break loops randomly. I believe he
> > was even te
On Thu, Sep 15, 2005 at 01:13:17PM -0400, Matt Fowles wrote:
> Nick~
>
> Dan's plan was to do a topographic sort of the object tree to avoid
> this problem for non-loops and to break loops randomly. I believe he
> was even tempted to call rand in there just to make sure people didn't
> come to de
On Sep 15, 2005, at 18:29, Nicholas Clark wrote:
On Wed, Sep 07, 2005 at 02:37:33PM +0200, Leopold Toetsch wrote:
Parrot calls the "destroy" vtable function for all PMCs that have
marked
themselves with PObj_active_destroy_FLAG, when the object gets
recycled
due to GC *or* at program exit.
Nick~
Dan's plan was to do a topographic sort of the object tree to avoid
this problem for non-loops and to break loops randomly. I believe he
was even tempted to call rand in there just to make sure people didn't
come to depend on a behavior...
I think it might be wise for us to make all the de
