Re: Garbage-collecting classes [was: This week's Summary]

2003-10-29 Thread Dan Sugalski
On Tue, 28 Oct 2003, Luke Palmer wrote: > > Object Instantiation > > Dan had a moment of clarity and declared that the Parrot Way to > > instantiate an object in class Foo will be: > > > > new P5, .Foo > > > > All we need now is a working implementation. And, apparently, knowin

Re: Garbage-collecting classes [was: This week's Summary]

2003-10-29 Thread Leopold Toetsch
Luke Palmer <[EMAIL PROTECTED]> wrote: > I do worry about some long-running daemon that uses anonymous classes > heavily. It's possible that after quite some time, we'd run out of > integers, Its the same problem as assigning PIDs to a process. We will have to cycle around and reuse old "free" n

Re: Garbage-collecting classes [was: This week's Summary]

2003-10-28 Thread Jeff Clites
On Oct 28, 2003, at 3:56 PM, Luke Palmer wrote: Object Instantiation Dan had a moment of clarity and declared that the Parrot Way to instantiate an object in class Foo will be: new P5, .Foo All we need now is a working implementation. And, apparently, knowing what class a

Garbage-collecting classes [was: This week's Summary]

2003-10-28 Thread Luke Palmer
> Object Instantiation > Dan had a moment of clarity and declared that the Parrot Way to > instantiate an object in class Foo will be: > > new P5, .Foo > > All we need now is a working implementation. And, apparently, knowing > what class a class is a member of might be ha