[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Set & Table hierarchy
- To: <mark>
 
- Subject: Set & Table hierarchy
 
- From: Eric Dean Tribble <tribble>
 
- Date: Thu, 16 Nov 89 21:25:59 PST
 
- Cc: <ravi>, <xtech>
 
- In-reply-to: <MarkS.Miller'smessageofTue>,56 PST <8911142023.AA12271@xanadu>
 
ScruSet<Heaper> :: count() stepper()
		      isEmpty() hasMember(x) isSubsetOf(s)
		      mutable() immutable()
   What do the "mutable" & "immutable" messages to a ScruSet mean?  I can
   think of several possibilities.
I think I made the suggestion for this.  They should actually be
asImmutable and asMutable.  asImmutable sent to a MuSet returns an
ImmuSet; sent to a MuTable returns an ImmuTable.  I would like the
conversion messages between different state-change types to be the
same for Set and Table classes.  It's easier to remember.
dean