P6FC

[Aldo Calpini]

hello everybody,
I'm just a poor newbie here, so please bear with me :-)

while reading the last Apocalypse I thought that maybe
time has come to write things down (like the recent
effort on properties), so I started to put down a tentative
class hierarchy of the Perl6 language (I call it P6FC for
Perl6 Foundation Classes, but the name may (should? :-)
very well change).

you can find what I've come up so far here:
http://dada.perl.it/p6fc.html

it's just plain ASCII for now, but I plan to have an XML
file with metadata attached (eg. bibliography, apocalypse
number, references and such) and a dynamically produced
SVG (or something else) graph.

probably I'm not the right person to mantain this (I already
have my problems following p6-internals and I'm not even
subscribed to p6-language), but I just wanted to throw
the idea out.

feel absolutely free to take over the whole stuff or reject
this in disgust :-)

cheers,
Aldo

__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;

[Murat Ünalan]

[snip]

> effort on properties), so I started to put down a tentative
> class hierarchy of the Perl6 language (I call it P6FC for
> Perl6 Foundation Classes, but the name may (should? :-) very
> well change).

A very good idea, but i am afraid that this ML isnt the right
audience.

PS: But before reinventing a wheel, i would like to suggest to
adopt the .NET/Java object hierarchy.

Murat

[Aldo Calpini]

Murat Ünalan wrote:
> A very good idea, but i am afraid that this ML isnt the right
> audience.
>
> 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 :-)

anyway, on http://dada.perl.it/p6fc.html you find now a pretty
GraphViz image accompanied by the XML data source (I'm digging up
the references right now) and the script I used to produce the
diagram.

any (possibly meaningful) feedback will be very appreciated.

[Simon Cozens]

da...@perl.it (Aldo Calpini) writes:
> any (possibly meaningful) feedback will be very appreciated.

I think Type should be called Value, and that arrays should possibly be a
mixin of lists, but apart from that it looks fine. Oh, and you missed
out Grammars; and I don't know if macros are actually objects and can be
tossed around, or if they're just part of the compilation process.

--
<Sauvin> Remember: amateurs built the Ark; _professionals_ built the
Titantic.

[Murat Ünalan]

[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