[519] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next next in chain last in chain last

Re: To-Do list..

daemon@ATHENA.MIT.EDU (Fri Nov 4 18:38:13 1994 )

From: Alex Stewart <riche@crl.com>
To: brandon@riverheights.declab.usu.edu
Date: Fri, 4 Nov 1994 15:36:21 -0800 (PST)
Cc: coldstuff@MIT.EDU
In-Reply-To: <9411042305.AA02851@riverheights.declab.usu.edu> from "brandon@riverheights.declab.usu.edu" at Nov 4, 94 04:05:38 pm

> Actually (cosmetic here), I'd prefer executables/ or exe_bin/, or hmm,
> execute_bin/ (hsm), perhaps execute/  (sigh).

Howabout exec/?

> "private" would be good too, in my opinion (would remove a lot of perm
> checking which simply checks to make sure it is called by this object).
> Also, I would (still) like to see the assignment operator change from '='
> to ':='.  I believe it would seriously help lessen confusion in the language,
> in relation to people learning the language.

Yeah, I forgot about these two when making up my list.. both of these should be
in the "discussion" section.

Something else I forgot which should be in the "to-do" section:

In-DB message->method resolution
  Originally (in the docs at least) there seemed to be some distinction between
  a message sent to an object and the method called upon receiving that object,
  but no real advantage of this conceptual distinction was taken.  I'm going to
  add the option for an object to do its own message resolution by way of a
  specific method on the object, which the server would call, if present, to
  find out what method should be executed when a message gets sent to that
  object.  In addition to enhancing encapsulation, this would also have
  significant advantages in several areas such as doppleganger frobs and
  network-object representations.

     Alex Stewart - riche@crl.com - Richelieu @ Diversity University MOO