On Mon, Apr 17, 2006 at 04:44:10PM +0200, Leopold Toetsch wrote:
> Thinking a bit more about it (and discussing this issue with pmichaud)
> on #parrot - it seems that we really want hierarchical class names too,
> the more that a Perl6 class isa NameSpace too.
>
> That means:
>
> * newclass, su
chromatic wrote:
What should the syntax for creating new objects be? That is, if I define an
object with its methods in the namespace [ 'PAST'; 'Node' ], how do I create
a new instance of that class?
.local pmc node
node = new ???
Thinking a bit more about it (and discussin
On Apr 17, 2006, at 8:02, chromatic wrote:
What should the syntax for creating new objects be? That is, if I
define an
object with its methods in the namespace [ 'PAST'; 'Node' ], how do I
create
a new instance of that class?
.local pmc node
node = new ???
.namespace ['PAS
On Sunday 16 April 2006 22:00, Chip Salzenberg wrote:
> * standard Parrot libraries not associated with any HLL should have their
> own namespaces
>
> For example, PGE should live in a ["pge"] namespace, or, conceivably,
> under ["parrot";"PGE"]. In any case, the current double colons a
Based on a status report from Leo {thanks!} and my recent revisions to
pdd21, here's a list of things that need to be done to bring parrot fully
into the new world of namespaces. The items are roughly in descending order
of importance. There's room for several contributors here
[[ NAMESPACE
