Such feature would incur a significant performance hit to all
applications. If you really need to get all instances of some class you
can e.g. monkey-patch its initialize method and store the instances in a
(weak) list. Although we could provide a command line option that would
allow us to match MRI’s semantics of each_object precisely, I don’t see
a strong use case for such feature. All use cases I have seen so far
could be implemented in much more efficient way that doesn’t rely on
From: [email protected]
[mailto:[email protected]] On Behalf Of Shay F.
Sent: Sunday, October 25, 2009 10:10 PM
To: [email protected]
Subject: Re: [Ironruby-core] Something’s wrong with ObjectSpace
I don’t have a specific need for that right now. However, it does sound
logical to me that you’d want to get all the strings in your
application. It becomes even more reasonable when you run each_object
with Thread, to find out all defined. This doesn’t work as well.
But, this is not the most used class out there so I IronRuby will
continue to ROCK despite that.
Thanks for the reply Tomas,
On Mon, Oct 26, 2009 at 1:00 AM, Tomas M.
<[email protected]mailto:[email protected]>
This is by design. We don’t support enumerating objects that are not
modules. A string instance is not a module.
Why do you need to enumerate all allocated strings?