Re: getLoc/setLoc

[glen e. p. ropella]

At 11:31 AM 4/30/98 -0700, you wrote:
>GR> Maybe the getLoc should be
>GR> changed to be something like getTypeAtLoc and setLoc should be
>GR> removed completely to avoid confusion between LocSymbols being
>GR> indices into a collection?
>
>Hypothetically, I'd be inclined to make a change to a completely new
>name like getMemberStatus.  In a `design' sense, removing setLoc would
>just be a question of how many theoretical sorts of collection index
>types couldn't support getOffset.

Well, thinking along the lines of Ken's recent bug report,
I would like to be able to set my pointer to any location
in a collection at which an index is pointed.  I suppose this
means that i'd like to make all collections randomly accessible
but with the ability to set the index and then use the normal
navigation tools after that.  So, for example, when using a 
Set, I would like to be able to do a "pointIndexAtMember: anObject"
as well as a "createIndexIn: aZone fromMember: anObject".

Even though a Set is not supposed to be "ordered" to any real
extent, I'd still like to be able to set the index and then 
begin picking objects out of the collection.  (An idea for
a "next" in a Set could be a randomly drawn object from the
Set.)

BTW, "createIndexIn: aZone fromMember: anObject" seems to be
a stub.  It should at least say, NotImplemented.

Would y'all be interested in incorporating code I add to 
collections?  Or is Roger still planning on finishing it?

glen

glen e. p. ropella         =>Hail Eris!<=         <address@hidden>
The Swarm Corporation                             (505) 424-0448

                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.
                  ==================================