Dan Sugalski wrote:
> Allow me to haul out this bucket of ice-water I keep around
> for just such an eventuality. :)
>
> There's a low limit to the complexity of any sort of traversal we can
> provide. We *can't* go recursive in a traversal, if it crosses the
> C->Parrot or Parrot->C boundary as
On Oct 27, 2003, at 6:21 AM, Dan Sugalski wrote:
On Fri, 24 Oct 2003, Gordon Henriksen wrote:
On Monday, October 20, 2003, at 11:40 , Jeff Clites wrote:
My solution was to define a new vtable method--I've called it
visit(),
though the name's not the important part--to which you pass a
callback
On Fri, 24 Oct 2003, Gordon Henriksen wrote:
> On Monday, October 20, 2003, at 11:40 , Jeff Clites wrote:
>
> > My solution was to define a new vtable method--I've called it visit(),
> > though the name's not the important part--to which you pass a callback
> > (plus an optional context argument).
On Monday, October 20, 2003, at 11:40 , Jeff Clites wrote:
My solution was to define a new vtable method--I've called it visit(),
though the name's not the important part--to which you pass a callback
(plus an optional context argument). It's job is to invoke that
callback on each of it's refer
As mentioned in a previous post, I've been working on getting ordered
destruction working. I actually have a mostly-working version of this
now, which will merit its own discussion, but there's a particular
aspect which I wanted to call out in light of Dan's recent post on
"Object freezing".
A
