Sam Tregar wrote:
> On Wed, 29 Aug 2001, Jeremy Howard wrote:
>
> > The answer used in .NET is to have a dispose() method (which is not a
> > special name--just an informal standard) that the class user calls
manually
> > to clean up resources. It's not an ideal solution but there doesn't seem
to
> > be many other practical options.
>
> Well, there's the Perl 5 reference counting solution. In normal cases
> DESTROY is called as soon as it can be. Of course we're all anxious to
> get into the leaky GC boat with Java and C# because we've heard it's
> faster. I wonder how fast it is when it's halfway under water and out of
> file descriptors.
>
I don't think speed is where the interest is coming from. GC should fix
common memory problems, such as the nasty circular references issue that has
caught all of us at some time.
