From: Sean O'Dell <sean@...>
Date: 2002-02-24T12:01:56+09:00
Subject: Re: Object/Memory Management

"Yohanes Santoso" <ysantoso@jenny-gnome.dyndns.org> wrote in message
news:DA9E35953D29B289.A8911961D9108EE8.C57F681E1F798B7F@lp.airnews.net...
> "Sean O'Dell" <sean@celsoft.com> writes:
>
> So, actually, it seems the use of grow-only memory pooling is quite
> common, but you don't notice it because the OS makes it painless.

I'm taking it on faith right now that Ruby will be fine with long-running
processes and having many different little Ruby processes going at the same
time along with everything else.  I don't know enough about the internals to
make a real judgement, so I'm taking everyone's word for it that it will be
fine.  If memory usage explodes on me, it explodes on me and I'll adjust my
usage of Ruby accordingly.

Dave Thomas helped me with ideas about how to handle the lack of object
destructors, so I believe I'm covered there.  I can still think of reasons
why I would need destructors, but so far I've been able to imagine ways
around it and I think the new way of doing things is simply going to become
my own personal paradigm while programming in Ruby.

Thanks for the help,

    Sean