[racket] Destroy object ?

From: Jay McCarthy (jay.mccarthy at gmail.com)
Date: Thu Sep 30 06:44:04 EDT 2010

The GC finds objects that you cannot refer to and deletes them. All
other objects have some way of getting to them (chains of field
references), so they are not deleted. If you want to delete something,
you can't do it. You can, however, destroy references to it (set them
to #f, for example), so that the GC will eventually discover that they
cannot be reached.

So, you don't have to send things there and you can't get the deleted data back.


On Thu, Sep 30, 2010 at 4:41 AM, Ted Vj Bros <tedr56 at gmail.com> wrote:
> Thanks for this fast answer.
> Unfortunatly, I'm familiar with this concept of garbage collector.
> have I to send my instances to there or is it a way to get deleted data back?
> Thanks.
>> It seems like your question is whether there is a garbage collector. There is.
>> Jay
>>> Hi the list,
>>> I'm a user of Fluxus http://www.pawfal.org/fluxus/
>>> which is a scheme environnement for 3D, audio and games.
>>> I'm trying to learn the racket Oriented Object style and asking myself a
>>> thing?
>>> How the objects can be deleted after their work?
>>> And are they overwrited if an another come to replace one, and the memory
>>> managed well for it?

Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University

"The glory of God is Intelligence" - D&C 93

Posted on the users mailing list.