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: 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