Re: Some random design notes

2002-01-10 Thread Dan Sugalski
At 10:43 PM 1/10/2002 +, Tim Bunce wrote: >On Thu, Jan 10, 2002 at 12:37:23PM -0500, Dan Sugalski wrote: > > > > >Tim [who's not really been paying attention, so ignore me if I'm being > daft]. > > > > Nah, you're making sense. Besides, vtables are all your fault in the first > > place, so I

Re: Some random design notes

2002-01-10 Thread Dan Sugalski
At 10:43 PM 1/10/2002 +, Tim Bunce wrote: >On Thu, Jan 10, 2002 at 12:37:23PM -0500, Dan Sugalski wrote: > > > > >Tim [who's not really been paying attention, so ignore me if I'm being > daft]. > > > > Nah, you're making sense. Besides, vtables are all your fault in the first > > place, so I

Re: Some random design notes

2002-01-10 Thread Tim Bunce
On Thu, Jan 10, 2002 at 12:37:23PM -0500, Dan Sugalski wrote: > > >Tim [who's not really been paying attention, so ignore me if I'm being daft]. > > Nah, you're making sense. Besides, vtables are all your fault in the first > place, so I ought to be listening... :) Why do I have the feeling th

Re: Some random design notes

2002-01-10 Thread Dan Sugalski
At 12:15 AM 1/10/2002 +, Tim Bunce wrote: >On Wed, Jan 09, 2002 at 04:42:51PM +, Graham Barr wrote: > > On Tue, Jan 08, 2002 at 06:38:02PM -0500, Dan Sugalski wrote: > > > ># Attributes are done as a hash of hashes. Each interpreter has a > > > ># pointer to an attribute hash, whose keys a

Re: Some random design notes

2002-01-09 Thread Tim Bunce
On Wed, Jan 09, 2002 at 04:42:51PM +, Graham Barr wrote: > On Tue, Jan 08, 2002 at 06:38:02PM -0500, Dan Sugalski wrote: > > ># Attributes are done as a hash of hashes. Each interpreter has a > > ># pointer to an attribute hash, whose keys are the attribute names. The > > ># values will be has

Re: Some random design notes

2002-01-09 Thread Graham Barr
On Tue, Jan 08, 2002 at 06:38:02PM -0500, Dan Sugalski wrote: > ># Attributes are done as a hash of hashes. Each interpreter has a > ># pointer to an attribute hash, whose keys are the attribute names. The > ># values will be hash pointers. Those hashes will each have a key which > ># is a PMC poi

Re: Some random design notes

2002-01-09 Thread Benoit Cerrina
> --- > > We need private methods for objects. > > --- just a comment on how this is done for ruby: #initially objects are created with a given class #say aFoo is an instance of class Foo aFoo = Foo.new #then we can add methods to aFoo def aFoo.bar() puts 'invoked bar' end #th

RE: Some random design notes

2002-01-08 Thread Dan Sugalski
At 01:47 PM 1/8/2002 -0800, Brent Dax wrote: >Dan Sugalski: ># This is just a collection of random notes I put together while serving ># jury duty. There's not much coherence here, but better to get it down ># than not. > >"Is this case worthy of the death penalty?" >"Hmm? Yeah, sure, whatever."

RE: Some random design notes

2002-01-08 Thread Brent Dax
Dan Sugalski: # This is just a collection of random notes I put together while serving # jury duty. There's not much coherence here, but better to get it down # than not. "Is this case worthy of the death penalty?" "Hmm? Yeah, sure, whatever." :^) # Global namespaces need to be multilevel the w

Some random design notes

2002-01-08 Thread Dan Sugalski
This is just a collection of random notes I put together while serving jury duty. There's not much coherence here, but better to get it down than not. --- Global namespaces need to be multilevel the way lexical spaces are. Ruby and Python both require this. (Well, it's not required but i