[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SELECTQ using = or EQ
- To: CWH at MIT-MC
- Subject: SELECTQ using = or EQ
- From: Glenn S. Burke <GSB at MIT-ML>
- Date: Fri, 17 Jul 81 20:02:00 GMT
- Cc: Steele at CMU-20C, JONL at MIT-MC, ALAN at MIT-MC, BUG-LISP at MIT-MC
- Original-date: 17 July 1981 16:02-EDT
Date: 17 July 1981 15:53-EDT
From: Carl W. Hoffman <CWH at MIT-MC>
Date: 17 July 1981 12:02-EDT
From: Jon L White <JONL at MIT-MC>
Fixed now. Prior to this buggy state, it produced a CASEQ,
which insists on either symbols or numbers, but not mixtures
Whoa, what's going on here. I've been assuming until now that
CASEQ and SELECTQ are just different names for the same thing.
Are you saying this is no longer the case?
The semantics of SELECTQ are leaning towards allowing "mixed types",
and those of CASEQ requiring everything to be of the same type.
"knowning" that everything is of the same type can help the compilation
of such a construct where that matters (pdp10 maclisp, for instance).
Elsewhere such a constraint doesn't hurt; you just use EQ all the time
anyway. Guy, are you there? Words of wisdom?