[snip]
> > PS: But before reinventing a wheel, i would like to suggest to
> > adopt the .NET/Java object hierarchy.
>
> uhm. either I am completely wrong or you are totally out
> of track. I really don't understand what you're talking about :-)
Urgs. Hopefully i didn't trapped into a dunghill ? But let me dig deeper
into it. Here an example class "Hashtable" from ".NET Framework Class
Library":
System.Collections Namespace
Classes
Class Description
Hashtable Represents a collection of key-and-value pairs
that are organized based on the hash code of the key.
[C#]
public class Hashtable : IDictionary, ICollection, IEnumerable,
ISerializable, IDeserializationCallback, ICloneable
> anyway, on http://dada.perl.it/p6fc.html you find now a
> pretty GraphViz image accompanied by the XML data source (I'm
Let me grab your suggestion for the example "Hash":
Hash isa Type
Type isa Object
What i intended is to go and "copy" the .NET/Java
object/interface/inheritance hierarchy (s.a.). So
Hash isa IDictionary, ICollection, IEnumerable, ISerializable,
IDeserializationCallback, ICloneable
etc..
> digging up the references right now) and the script I used to
> produce the diagram.
>
> any (possibly meaningful) feedback will be very appreciated.
>
>
> cheers,
> Aldo
Murat
