memorial ballot

[Dave Dyer <DDYER@USC-ISIB>]

1. Eliminate PARSE-NUMBER	    Yes.
2. LOOP => BLOCK NIL		    Yes.
3. GET-INTERNAL/REAL-TIME	    Yes.
4. Macro expansions are portable.   Yes.
5. :allow-other-keys		    No opinion
6. (multiple-value (...nil...)...)  Yes, and YES for multiple valuebind as
				    Why should I have write my own LET when
				    i want to ignore one of the values?  
7. Flush CATCH-ALL, UNWIND-ALL	    NO!  Otherwise there is no way to escape
				    the predefined error semantics.  These
				    provide the essential gross hook that
				    allows implementation of whatever variant
				    is necessary.  Example: The oly kind of
			            CATCH Interlisp HAS is effectively
				    CATCH-ALL
8. DEFMACRO destructuring.	    Yes.
9. PROCLAIM			    No, if it is really unnecessary.
10. SIMPLE-VECTOR holds any object  I suppose.
			            Do I hear a proposal for 
				    "SIMPLE SIMPLE VECTORS"?
11. FILL-POINTER		    Yes.
12. :NAMED in MAKE-ARRAY, MAKE-VECTOR	Yes.  Element 0 holds the name.
13. *READ-BASE*			    Yes.
14. SUB-READ, SUB-R-D-L		    No opinion
15. *PRINfoo* => *PRINT-foo*	    Yes.
16. ~E,~F,~G like in Fortran	    Yes.
17. Flush MAXPREFIX,MAXSUFFIX	    Yes.
18. | : interaction		    No.
19. ~:A vs NIL vs ()		    Yes.
20. APROPOS, PPRINT return NIL	    Ok. Rather than a separate family to 
				    specify type of results, 
				    I'd prefer an optional argument to specify
				    what to do.  I usually use
					NIL->PRINT
					T-> return list
				         otherwise (APPLY* X --) and
						return list of non-nil results
				    
21. *features* are keywords	    No opinion.

-------