Re: Classes moving into namespaces; parrot reserved namespace

2006-05-24 Thread Chip Salzenberg
On Thu, May 25, 2006 at 01:09:47AM +0100, Jonathan Worthington wrote: > This looks pretty nice. Sometimes "dynamic" is remarkably convenient. :-) > 1) (Can we|Will we be able to) do the whole newclass/addattribute/addmethod > thing at compile time (in a :immediate), so that you have your classe

Re: Classes moving into namespaces; parrot reserved namespace

2006-05-24 Thread Jonathan Worthington
"Chip Salzenberg" <[EMAIL PROTECTED]> wrote: I've got a partial solution to the pending question of namespace vs. class. Specifically, I've realized that Parrot already had most of a simple solution to populating a class's methods even if the class has no public namespace, what with the ".const

Re: Classes moving into namespaces; parrot reserved namespace

2006-05-23 Thread Chip Salzenberg
I've got a partial solution to the pending question of namespace vs. class. Specifically, I've realized that Parrot already had most of a simple solution to populating a class's methods even if the class has no public namespace, what with the ".const .Sub" technique. When I went to implement the r

Re: [ARCH] Classes moving into namespaces; parrot reserved namespace

2006-05-19 Thread Leopold Toetsch
On May 16, 2006, at 19:32, Chip Salzenberg wrote: There's is a problem with the naming of classes and their associated namespaces that must be addressed. The first question is: why is the namespace associated, or - in other words - why does a class C a namespace instead of C namespace. The

Re: Classes moving into namespaces; parrot reserved namespace

2006-05-18 Thread Chip Salzenberg
{ copied to P6L for the "use case" question below } On Wed, May 17, 2006 at 12:18:27PM -0400, Will Coleda wrote: > My concern is that, in an effort to work around this restriction, > each language will end up implementing a workaround to hide the > __parrot* namespaces: these workarounds will

Re: [ARCH] Classes moving into namespaces; parrot reserved namespace

2006-05-17 Thread Will Coleda
Chip, we briefly discussed this on IRC yesterday, but I wanted to make sure this didn't get lost. I don't like the impact that this is going to have on HLL languages - it's exposing internal bits of parrot to the HLL programmers. The argument that we already expose some bits (for example, c

[ARCH] Classes moving into namespaces; parrot reserved namespace

2006-05-16 Thread Chip Salzenberg
There's is a problem with the naming of classes and their associated namespaces that must be addressed. Creating Parrot classes currently requires _typed_ namespaces, that is, namespaces where more than one object can have the same fully-qualified name. Parrot's default namespace allows that ther