[DGD] Keeping track of clones

[Erwin Harte]

On 8/26/05 11:10 PM Steve Wooster wrote:
> On 26 Aug 2005 at 13:46, Felix A. Croes wrote:
> 
>>When the object has a pending callout, all of it will be swapped in.
> 
> 
> Do you mean that an object will remain swapped in while it has a callout pending, or 
> do you mean that when the callout expires, its associated function call swaps the 
> object back in? (I assume the latter, but because your wording is a little ambiguous, I 
> figured I should make sure)

The latter is true, indeed.  Having pending callouts is no reason in and 
off itself to keep an object swapped in.  Just imagine a pending callout 
that'll run in an hour, or a day. :)

However, I interpreted his reply to say that when you apply status(ob) on 
an object with one or more pending callouts, all of it will be swapped in, 
implying that if there aren't, some parts aren't.  I would assume the 
data-sectors, because all the other status(ob) results _look_ to be things 
you can provide with just the code-sectors, whereas the the 
status(ob)[O_CALLOUTS] section refers to the function-parameters, for 
instance, which would be stored in the data-sectors.

Hope that helps,

Erwin.
-- 
Erwin Harte <harte at is-here.com>