Re: Need help with Class-Allocated Slots

• To: Hugh Greene <q@tardis.ed.ac.uk>
• Subject: Re: Need help with Class-Allocated Slots
• From: P T Withington <ptw@callitrope.com>
• Date: Wed, 28 Jun 2000 14:48:44 -0400
• CC: <info-dylan@ai.mit.edu>
• In-Reply-To: <Pine.GSO.3.96.1000628164507.4116B-100000@tardis.tardis.ed.ac.uk>
• Sender: owner-info-dylan@ai.mit.edu
• User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022

Hugh Greene q@tardis.ed.ac.uk on  2000-06-28 12:15 wrote:

>> ...  And the class itself can't be GC'ed until you can
>> prove that nobody will ever call 'make' on the class again.
> 
> Classes created with "make(<class>, ...)" might become unreachable at some
> point and hence get GCd.  Not common practice, but possible.

I seem to recall Java had a bug where they unloaded a package if there were
no instances of its class on the assumption there was no state in the class
and any attempt to make a new instance could simply reload the package, but
class slots clearly are state.

• Re: Need help with Class-Allocated Slots
• From: Hugh Greene <q@tardis.ed.ac.uk>

• Prev: Re: Need help with Class-Allocated Slots
• Next: DUIM font question
• Index(es):
  • Main
  • Thread