I am working on big object trees (see my scratch pad for an overview if you're curious) and thought I'd comment on a problem you seem to have with memory leaks (according to your CPAN docs).
You consider inside out objects? Those seem cool, but ... new.
I don't store references in objects -- the objects store short Id strings. A central "objOwner" object hands out the objects from the Ids. It looks like this:
my($superObj) = $o->GetObject($o->GetSupId());
I did it like that because I thought it would be easier to test, less error prone and would make it easier to save/restore parts of the object tree (also easier to stub for rpc).
That it helps the GC algorithm I put under "easier to test".
This should be clear? Ask otherwise. (I hope to upload to CPAN in a few weeks. Writes examples and UI now... :-( )
In reply to Re: CPAN indexes *.pm as "Documentation"? (Memory leaks)
by BerntB
in thread CPAN indexes *.pm as "Documentation"?
by rvosa
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |