Re^5: CPAN indexes *.pm as "Documentation"? (Memory leaks)

The main reason I am thinking about the array-index-as-object approach is that this might be the approach people I work with will adopt also as a serialization format to transmit trees

Ah... good reason. I have a presentation API on top of my work code that would be easy to stub and use RPC calls to other languages.

I'm a bit unclear what you mean by links.

References to objects outside of the direct inheritance hierarchy. (Nothing you need, I'd guess.) I don't want code to store the IDs in strings or something because they might be renumbered. If e.g. a part of an object definition are to be copied into some other place.

Do you have your code on CPAN or something?

The code is mostly done. I am writing a simple CGI user interface, will do some example and trying to force myself to write documentation. :-)

Give it a couple of weeks (I've said that for a month :-( ).

Comment on Re^5: CPAN indexes *.pm as "Documentation"? (Memory leaks)

Replies are listed 'Best First'.
Re^6: CPAN indexes *.pm as "Documentation"? (Memory leaks) by rvosa (Curate) on Oct 03, 2005 at 08:00 UTC
References to objects outside of the direct inheritance hierarchy. (Nothing you need, I'd guess.) I don't want code to store the IDs in strings or something because they might be renumbered. If e.g. a part of an object definition are to be copied into some other place. "Has-a" versus "Is-a" relationships? That's what's bugging me: nodes on trees (especially terminal nodes) ought to be crossreferenced with Operational Taxonomic Units (more sane people would call them "species"...), which in turn ought to be crossreferenced with comparative data (e.g. DNA sequences). None of these relationships are through inheritance, but more data-oriented rather than object-oriented. This all works in that I have methods to match up the different types of information by species name, and build references between the objects - but now everything is one network of circular references that I'm pretty sure keeps floating somewhere in RAM space after it's gone out of scope (sidenote: how might you test that???). I'm interested to see how you go about doing that, so will you post a message to announce your module?	[reply]

Replies are listed 'Best First'.

Re^6: CPAN indexes *.pm as "Documentation"? (Memory leaks)
by rvosa (Curate) on Oct 03, 2005 at 08:00 UTC

References to objects outside of the direct inheritance hierarchy. (Nothing you need, I'd guess.) I don't want code to store the IDs in strings or something because they might be renumbered. If e.g. a part of an object definition are to be copied into some other place.

[reply]