I see your point. While ObjectSpace.each_object can be limited to
objects of a certain class or module, it doesn't help when neither is
certain. On the other hand, would it be possible to extend ObjectSpace
to keep such lists? I'm just going with the reuse, reduce, recycle
principle
   -CWS

On Fri, 23 Jul 2004 20:16:58 +0900, Robert Klemme <bob.news / gmx.net> wrote:
> 
> "Claus Spitzer" <DocBoobenstein / gmail.com> schrieb im Newsbeitrag
> news:a7c2a819040722182673c1c41 / mail.gmail.com...
> > Traversing object networks... that seems like an application for
> > ObjectSpace.each_object
> 
> No, he rather means, doing a graph search on a set of connected objects.
> ObjectSpace.each_object won't help you there, because that yields *all*
> objects.  Typically you're only interested in a certain sub set, i.e. all
> objects that were retrieved from some persistent store within a single
> transaction (so you can write them all back) etc.
> 
> Regards
> 
>     robert
> 
>