Re: What the heck is: timely destruction

2003-09-05 Thread Steve Fink
Tim Bunce wrote: On Sun, Aug 24, 2003 at 10:48:02AM -0700, Steve Fink wrote: I guess you could think of the lifecycle of an individual object as being controlled by a few significant life events: 1. birth 2. the last reference disappearing 3. finalization 4. destruction That's a nice idea,

Re: What the heck is: timely destruction

2003-08-24 Thread Nicholas Clark
On Sun, Aug 24, 2003 at 09:44:52PM +0100, Tim Bunce wrote: > On Sun, Aug 24, 2003 at 10:48:02AM -0700, Steve Fink wrote: > > I guess you could think of the lifecycle of an individual object as > > being controlled by a few significant life events: > > > > 1. birth > > 2. the last reference disa

Re: What the heck is: timely destruction

2003-08-24 Thread Tim Bunce
On Sun, Aug 24, 2003 at 10:48:02AM -0700, Steve Fink wrote: > It would probably make discussion easier if people switched to using > better terminology. I prefer using "destruction" to mean the memory > for an object actually getting freed, and "finalization" for whatever > cleanup actions an objec

Re: What the heck is: timely destruction

2003-08-24 Thread Dan Sugalski
At 6:45 PM -0700 8/18/03, Dave Whipp wrote: "Benjamin Goldberg" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] What we'd like is a way (and there've been a couple proposed) to make it so that the sweep at the end of scope can *quickly* determine that all objects needing timely destr

Re: What the heck is: timely destruction

2003-08-24 Thread Steve Fink
It would probably make discussion easier if people switched to using better terminology. I prefer using "destruction" to mean the memory for an object actually getting freed, and "finalization" for whatever cleanup actions an object performs at some point after it is no longer accessible. So "timel

Re: What the heck is: timely destruction

2003-08-19 Thread Luke Palmer
"Leopold Toetsch" <[EMAIL PROTECTED]> > To: "Benjamin Goldberg" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, August 19, 2003 12:20 AM > Subject: Re: What the heck is: timely destruction > > > > Benjamin Goldberg

Re: What the heck is: timely destruction

2003-08-19 Thread Piers Cawley
Bennett Todd <[EMAIL PROTECTED]> writes: > Is the destruction going to be timely enough for > > IO::File->new(">foo")->print("foo\n"); > print `cat foo`; > > to behave predictably? That's certainly the idea.

Re: What the heck is: timely destruction

2003-08-19 Thread Dan Sugalski
On Tue, 19 Aug 2003, Bennett Todd wrote: > Is the destruction going to be timely enough for > > IO::File->new(">foo")->print("foo\n"); > print `cat foo`; > > to behave predictably? If you're asking if you can, in general, count on statement level timely destruction of arbitrary

Re: What the heck is: timely destruction

2003-08-19 Thread Bennett Todd
Is the destruction going to be timely enough for IO::File->new(">foo")->print("foo\n"); print `cat foo`; to behave predictably? -Bennett pgp0.pgp Description: PGP signature

Re: What the heck is: timely destruction

2003-08-19 Thread K Stol
, August 19, 2003 12:20 AM Subject: Re: What the heck is: timely destruction > Benjamin Goldberg <[EMAIL PROTECTED]> wrote: > > > Every time we come to a scope end, we do a garbage collection run. > > ... only if there are objects around, that were marked to need timely >

Re: What the heck is: timely destruction

2003-08-19 Thread Leopold Toetsch
Dave Whipp <[EMAIL PROTECTED]> wrote: > ... I've run into this problem on several GCed apps: the sweep > destroys locality of access, causing pages to be loaded that the application > doesn't need. This can cause a very abrupt performance drop. The flags used during DOD take (for simple PMCs) jus

Re: What the heck is: timely destruction

2003-08-19 Thread Dave Whipp
"Benjamin Goldberg" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > What we'd like is a way (and there've been a couple proposed) to make it > so that the sweep at the end of scope can *quickly* determine that all > objects needing timely destruction are still alive/reachabe/in-scope,

Re: What the heck is: timely destruction

2003-08-19 Thread Leopold Toetsch
Benjamin Goldberg <[EMAIL PROTECTED]> wrote: > Every time we come to a scope end, we do a garbage collection run. ... only if there are objects around, that were marked to need timely destruction. If the HLL will decide that each object might need timely destructions we will get into troubles, at

Re: What the heck is: timely destruction

2003-08-18 Thread Benjamin Goldberg
Michael G Schwern wrote: [snip stuff, including a mention of refcounting and it's (dis)advantages] > So Parrot is going with something else. Don't ask me what it is, I > don't know. Parrot will do it like Java -- a mark-and-sweep garbage collector -- with the difference that garbage collection wi

Re: What the heck is: timely destruction

2003-08-18 Thread Bennett Todd
2003-08-18T13:52:50 K Stol: > After reading most of the messages on timely destruction, I still > don't quite understand what it is. If someone has a spare minute > free, could you please explain? The other explanations certainly have formality to commend them, but somehow they didn't make clear t

Re: What the heck is: timely destruction

2003-08-18 Thread Elizabeth Mattijsen
At 11:56 -0700 8/18/03, K Stol wrote: Uhm, I didn't realize destructor methods were called, but now I see that's the whole point: destructor methods should be called when doing timely destruction. You already said just now: This doesn't necessarily mean that their memory has to be freed but that

Re: What the heck is: timely destruction

2003-08-18 Thread Michael G Schwern
On Mon, Aug 18, 2003 at 11:56:53AM -0700, K Stol wrote: > > This doesn't necessarily mean that their memory has to be freed but that > > at least their destructor methods are called. > > So the objects may be still in memory. I thought the fact that they are > still in memory > was troublesome, bu

Re: What the heck is: timely destruction

2003-08-18 Thread Michael G Schwern
On Mon, Aug 18, 2003 at 11:38:22AM -0700, K Stol wrote: > if I understood correctly, the problem is that some objects should be > destroyed *immediately*, and should not wait for the GC. Yep. In perl 5 *all* objects and variables are to be destroyed immediately. This doesn't necessarily mean tha

Re: What the heck is: timely destruction

2003-08-18 Thread K Stol
- Original Message - From: "Elizabeth Mattijsen" <[EMAIL PROTECTED]> To: "K Stol" <[EMAIL PROTECTED]>; "Michael G Schwern" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, August 18, 2003 3:10 AM Subject: Re: What the heck is:

Re: What the heck is: timely destruction

2003-08-18 Thread K Stol
- Original Message - From: "Michael G Schwern" <[EMAIL PROTECTED]> To: "K Stol" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, August 18, 2003 2:49 AM Subject: Re: What the heck is: timely destruction > On Mon, Aug 18, 2003 at

Re: What the heck is: timely destruction

2003-08-18 Thread K Stol
- Original Message - From: "Michael G Schwern" <[EMAIL PROTECTED]> To: "K Stol" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, August 18, 2003 2:04 AM Subject: Re: What the heck is: timely destruction > On Mon, Aug 18, 2003 at 10:52:50

Re: What the heck is: timely destruction

2003-08-18 Thread Michael G Schwern
On Mon, Aug 18, 2003 at 10:52:50AM -0700, K Stol wrote: > After reading most of the messages on timely destruction, I still don't quite > understand what it is. If someone has a spare minute free, could you please explain? In perl5 you can write this. my $Destroyed = 0; sub DESTROY { $Destroyed

What the heck is: timely destruction

2003-08-18 Thread K Stol
hello, After reading most of the messages on timely destruction, I still don't quite understand what it is. If someone has a spare minute free, could you please explain? Thanks in advance! Klaas-Jan