[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CLOS vs. subtypes of FLOAT

	Date: 21 May 87 12:07 PDT
	From: Masinter.pa

	You omitted the possibility where all the classes
	exist in all implementations, but that some of the
	classes might be empty (have no instances) in some

In putting together the proposals, I had two (unfortunately unstated) design criteria:

   1) Discrimination on the subtypes of FLOAT should be allowed
   2) Discriminations that cannot work in a given implementation
      (due to collapsing together some of the subtypes) should signal
      an error so that the user doesn't lose quietly.

Proposal NONE loses on the first criterion and your proposal violates the second.