Mail Thread Index

• Date Index

• [no subject], Kent M. Pitman
• Re: #/char, Jon L White
• Re: character objects & randomness, Alan Bawden
  • <Possible follow-ups>
  • Re: character objects & randomness, Robert W . Kerns
  • Re: character objects & randomness, Jonathan A . Rees
  • Re: character objects & randomness, Jonathan A . Rees
  • Re: character objects & randomness, Guy . Steele at CMU-10A
• Re: eval-when, Daniel L . Weinreb
  • <Possible follow-ups>
  • Re: eval-when, Alan Bawden
  • Re: eval-when, Daniel L . Weinreb
  • Re: eval-when, Bernard S . Greenberg
  • Re: eval-when, David A . Moon
  • Re: eval-when, Greenberg . Multics at MIT-Multics
  • Re: eval-when, Daniel L . Weinreb
• Re: #/ returning a "character object", David A. Moon
  • <Possible follow-ups>
  • Re: #/ returning a "character object", Guy . Steele at CMU-10A
• [no subject], Kent M . Pitman
• Re: Confusion over character objects, Robert W . Kerns
• Re: Character objects, Robert W . Kerns
  • <Possible follow-ups>
  • Re: character objects, David A . Moon
  • Re: character objects, Guy . Steele at CMU-10A
• Re: character objects & representation issues, Alan Bawden
  • <Possible follow-ups>
  • Re: character objects & representation issues, Daniel L . Weinreb
  • Re: character objects & representation issues, Robert W . Kerns
  • Re: character objects & representation issues, Daniel L . Weinreb
• Re: Bawden's remarks on characters, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Bawden's remarks on characters, Mike McMahon
  • Re: Bawden's remarks on characters, Daniel L . Weinreb
• Re: generic types vs. specific types, Richard M. Stallman
  • <Possible follow-ups>
  • Re: generic types vs. specific types, Daniel L . Weinreb
• Re: CHPROP problems, RMS at MIT-AI
  • <Possible follow-ups>
  • Re: CHPROP problems, DLW at MIT-AI
  • Re: CHPROP problems, Robert W . Kerns
  • Re: CHPROP problems, Daniel L . Weinreb
• Re: Proposal #3 for MacLISP characters..., Kent M . Pitman
• Re: characters, Richard J . Fateman
  • <Possible follow-ups>
  • Re: characters, Robert W . Kerns
• Re: "completely wrong", Robert W . Kerns
• Re: "And even if you don't like your code to be readable (sorry)", Richard M. Stallman
  • <Possible follow-ups>
  • Re: "And even if you don't like your code to be readable (sorry)", Robert W . Kerns
• [no subject], Carl W . Hoffman
• Re: Character Objects (what else!), TK at MIT-AI
  • <Possible follow-ups>
  • Re: Character Objects (what else!), Robert W . Kerns
• Re: unwinding-scope, MOON5 at MIT-AI
  • <Possible follow-ups>
  • Re: UNWINDING-SCOPE, Robert W . Kerns
  • Re: unwinding-scope, Edward Barton
• Re: In reply to TK: Character Objects (what else!), DLW at MIT-AI
• Re: Request for comments (not about characters and fixnums!), Edward Barton
• Re: In reply to EB: unwind-protect, Daniel L . Weinreb
• [no subject], Robert W . Kerns
• [no subject], Carl W . Hoffman
• Re: UNWIND-PROTECT proposal (clarification), Edward Barton
• [no subject], Richard M. Stallman
• [no subject], Richard M. Stallman
• [no subject], Daniel L . Weinreb
• Re: amazing..., Chris Ryland
• Re: Red face, Robert W . Kerns
• [no subject], Robert W . Kerns
• [no subject], Robert W . Kerns
• Re: macro/expr property selection by funcall, Glenn S . Burke
• [no subject], Richard M. Stallman
• Re: Generalized LET due to RMS, Guy . Steele at CMU-10A
• Re: /* ... */, Alan Bawden
• Re: comment brackets, CSVAX . jkf at Berkeley
• Re: Suggestion for commenting brackets like /*...*/, Guy . Steele at CMU-10A
• Re: Multiple values, Guy . Steele at CMU-10A
• Re: #\EOF, Kent M . Pitman
  • <Possible follow-ups>
  • Re: #\EOF, David A . Moon
  • Re: #\EOF, George J . Carrette
  • Re: #\EOF, Kent M . Pitman
  • Re: #\EOF, Daniel L. Weinreb
  • Re: #\EOF, Kent M . Pitman
  • Re: #\EOF, Kent M . Pitman
  • Re: #\EOF, David A . Moon
• Re: #\EOF (look before you leap), David A . Moon
• Re: eof, Richard M. Stallman
  • <Possible follow-ups>
  • Re: eof, Guy . Steele at CMU-10A
• Re: #\EOF ... Yes, again., Kent M . Pitman
  • <Possible follow-ups>
  • Re: #\EOF ... Yes, again., CSVAX . jkf at Berkeley
  • Re: #\EOF ... Yes, again., Daniel L . Weinreb
  • Re: #\EOF ... Yes, again., Alan Bawden
  • Re: #\EOF ... Yes, again., Daniel L . Weinreb
  • Re: #\EOF ... Yes, again., Kent M . Pitman
  • Re: #\EOF ... Yes, again., David A . Moon
• Re: "What are you going to do about...", Daniel L . Weinreb
• Re: destructuring and &mumbles, Alan Bawden
  • <Possible follow-ups>
  • Re: destructuring and &mumbles, Daniel L . Weinreb
  • Re: destructuring and &mumbles, Alan Bawden
• Re: #| ... |#, Kent M . Pitman
  • <Possible follow-ups>
  • Re: #| ... |#, Guy . Steele at CMU-10A
  • Re: #| ... |#, Alan Bawden
  • Re: #| ... |#, Alan Bawden
• [no subject], Kent M . Pitman
• Re: #| One last comment on #| |#, Kent M . Pitman
  • <Possible follow-ups>
  • Re: #| One last comment on #| |#, Richard Mark Soley
  • Re: #| One last comment on #| |#, Guy . Steele at CMU-10A
  • Re: #| One last comment on #| |#, Daniel L . Weinreb
  • Re: #| One last comment on #| |#, Glenn S . Burke
• Re: Dave Touretzky's message on macros, destructuring, and functions, Kent M . Pitman
  • <Possible follow-ups>
  • Re: Dave Touretzky's message on macros, destructuring, and functions, Daniel L . Weinreb
• Re: #|...|#, Guy . Steele at CMU-10A
• Re: Clearing up a fine point in your reply to Touretzky, Kent M . Pitman
• Re: Nesting, Kent M . Pitman
• Re: #| ... |# = /* ... */, Dave Andre
• Re: Use of strings in PDP10 MACLISP, Jon L White
• Re: destructuring within "argument" positions, Jon L White
• [no subject], Richard M. Stallman
• Re: DIGITP not yet resolved?, Jon L White
  • <Possible follow-ups>
  • Re: DIGITP not yet resolved?, Daniel L . Weinreb
• [no subject], Richard M. Stallman
• [no subject], Richard M. Stallman
• Re: DIGITP, KMP at MIT-MC , JAR at MIT-MC
  • <Possible follow-ups>
  • Re: DIGITP, Guy . Steele at CMU-10A
  • Re: DIGITP, Howard I . Cannon
  • Re: DIGITP, Daniel L . Weinreb
  • Re: DIGITP, Carl W . Hoffman
  • Re: DIGITP, Daniel L . Weinreb
  • Re: DIGITP, Guy . Steele at CMU-10A
• Re: MacLisp strings, Barry Margolin
• Re: KMP and JAR proposal for DIGITP, Daniel L . Weinreb
• Re: Destructuring syntax, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Destructuring syntax, Jon L White
  • Re: Destructuring syntax, Daniel L . Weinreb
• Re: DIGIT-WEIGHT, Kent M . Pitman
• Re: DIGITP's second arg, and error conditions, Jon L White
• Re: DIGITP and the hair in ROMAN, Guy . Steele at CMU-10A
• Re: JONL's recenbt note on DIGITP, Guy . Steele at CMU-10A
• Re: Why DIGITP and DIGIT-WEIGHT?, Kent M . Pitman
  • <Possible follow-ups>
  • Re: Why DIGITP and DIGIT-WEIGHT?, Glenn S . Burke
• Re: DIGITP and DIGIT-WEIGHT, George J . Carrette
  • <Possible follow-ups>
  • Re: DIGITP and DIGIT-WEIGHT, Guy . Steele at CMU-10A
• Re: #|, Richard M. Stallman
• Re: Ooops, forgot to send this to LISP-FORUM, Guy . Steele at CMU-10A
• Re: Function invocation by key word, William A. Kornfeld
  • <Possible follow-ups>
  • Re: Function invocation by key word, Daniel L . Weinreb
• Re: DIGIT-WEIGHT/DIGITP and funny input bases, Robert W . Kerns
  • <Possible follow-ups>
  • Re: DIGIT-WEIGHT/DIGITP and funny input bases, George J . Carrette
  • Re: DIGIT-WEIGHT/DIGITP and funny input bases, Robert W . Kerns
  • Re: DIGIT-WEIGHT/DIGITP and funny input bases, Kent M . Pitman
  • Re: DIGIT-WEIGHT/DIGITP and funny input bases, Glenn S . Burke
  • Re: DIGIT-WEIGHT/DIGITP and funny input bases, Robert W . Kerns
  • Re: DIGIT-WEIGHT/DIGITP and funny input bases, Robert W . Kerns
  • Re: DIGIT-WEIGHT/DIGITP and funny input bases, Glenn S . Burke
  • Re: DIGIT-WEIGHT/DIGITP and funny input bases, Barry Margolin
• [no subject], Richard M. Stallman
• Re: DIGIT-WEIGHT etc., Quux at CMU-10A
• Re: Destructuring, GLS's and RMS's suggestions, and &EVAL., Jon L White
• Re: side effects and a complr bug., George J . Carrette
• Re: DEFUN-KEYED., George J . Carrette
• [no subject], Quux at CMU-10A
• Re: Thoughts on Completing Readers, Kent M . Pitman
• Re: A (possibly interesting) macro, William A. Kornfeld
  • <Possible follow-ups>
  • Re: A (possibly interesting) macro, George J . Carrette
• Re: SEQ, Kent M . Pitman
• Re: Why not SUBST, Kent M . Pitman
• [no subject], George J . Carrette
• Re: (setf (setq x (car y)) z), Alan Bawden
• [no subject], Thomas A . Boyle
• Re: from a Christian Science Monitor article on software, JoSH
  • <Possible follow-ups>
  • Re: from a Christian Science Monitor article on software, Robert W . Kerns
  • Re: from a Christian Science Monitor article on software, JWALKER at BBNA
  • Re: from a Christian Science Monitor article on software, George J . Carrette
• Re: Globe Article on Lisp, HGBaker . Symbolics at MIT-Multics
• [no subject], William A. Kornfeld
• Re: CSM article on software, Dave Andre
• Re: Unsolicited Plaudits, Jon L White
• Re: franz times, CSVAX . fateman at Berkeley
• [no subject], George J . Carrette
• [no subject], Richard L . Bryan
• Re: LABELS, GOSUB (yech), etc., Guy . Steele at CMU-10A
• [no subject], Daniel L . Weinreb
• [no subject], George J . Carrette
• [no subject], Daniel L . Weinreb
• Re: GOSUX, Robert W . Kerns
• Re: Time and time again, Scott J . Kramer
• Re: Response to Goto's lisp timings, Jon L White
• Re: DEFINEM, Guy . Steele at CMU-10A
• Re: SKIPE and SKIPN, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: SKIPE and SKIPN, Daniel L . Weinreb
• Re: UUOLINKS and numbers..., Guy . Steele at CMU-10A
• Re: Format's C, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Format's C, Alan Bawden
• Re: JSA/SRA, Robert W . Kerns
• Re: Apple OWL Lisp timings, HGBaker . Symbolics at MIT-Multics
• Re: What it may mean., Jon L White
• Re: SKIPE and SKIPN... and JSR, Guy . Steele at CMU-10A
• Re: PROG tags, Daniel L . Weinreb
• [no subject], George J . Carrette
• [no subject], Daniel L . Weinreb
• Re: forcibly stuffing features into a form, ie, PROG ramming, JoSH
• Re: Line numbers, J . Noel Chiappa
  • <Possible follow-ups>
  • Re: Line numbers, George J . Carrette
  • Re: Line numbers, Guy . Steele at CMU-10A
• Re: Line numbers and such, Daniel L . Weinreb
• [no subject], George J . Carrette
• Re: Improving LISP "grossly", Barry Margolin
  • <Possible follow-ups>
  • Re: Improving LISP "grossly", George J . Carrette
• Re: ENOUGH!, Alan Bawden
• Re: Incompatibility, Guy . Steele at CMU-10A
• Re: Line numbers and finite-state machines in LISP, Guy . Steele at CMU-10A
• Re: Twenex CURSORPOS, Jon L White
• Re: SXHASH, Jon L White
  • <Possible follow-ups>
  • Re: SXHASH, George J . Carrette
  • Re: SXHASH, Guy . Steele at CMU-10A
• Re: Poor ROTten SXHASH, Jon L White
  • <Possible follow-ups>
  • Re: Poor ROTten SXHASH, Guy . Steele at CMU-10A
• Re: Lispm SXHASH loses worse than you think., William A. Kornfeld
• Re: *CATCH/*THROW -- CATCH/THROW, Kent M . Pitman
• Re: Nutz!, Alan Bawden
• Re: MAKE-LIST, Jon L White
  • <Possible follow-ups>
  • Re: MAKE-LIST, Daniel L . Weinreb
  • Re: MAKE-LIST, George J . Carrette
• Re: Compromise?, Jon L White
• Re: MAKE-LIST -- Compromise? Please, not that way ..., Kent M . Pitman
• Re: MAKE-LIST -- compromise or not?, Jon L White
• Re: What can LISPM community do about MAKE-LIST, jonl at MIT-MC , kmp at MIT-MC
  • <Possible follow-ups>
  • Re: What can LISPM community do about MAKE-LIST, Daniel L . Weinreb
• Re: MAKE-LIST kludge, Guy . Steele at CMU-10A
• Re: Using * in names, Guy . Steele at CMU-10A
• Re: *****Idea!, Kent M . Pitman
• Re: Improving the LISP working environment by taking a lesson from..., Deutsch at PARC-MAXC
  • <Possible follow-ups>
  • Re: Improving the LISP working environment by taking a lesson from..., Daniel L . Weinreb
  • Re: Improving the LISP working environment by taking a lesson from..., Richard M . Stallman
  • Re: Improving the LISP working environment by taking a lesson from..., Jeffrey Shrager
• Re: Using macros in Mapping functions, Charles Rich
  • <Possible follow-ups>
  • Re: Using macros in Mapping functions, Earl A . Killian
  • Re: Using macros in Mapping functions, David A . Moon
  • Re: Using macros in Mapping functions, Charles Rich
• Re: Muddy diamonds, Kent M . Pitman
• Re: Of diamonds and mud:, Daniel L . Weinreb
  • <Possible follow-ups>
  • Re: Of diamonds and mud:, Guy . Steele at CMU-10A
  • Re: Of diamonds and mud:, Jeffrey Shrager
• Re: lisp vs apl, JoSH
• [no subject], Richard M. Stallman
• Re: APL and LISP, Alan Bawden
  • <Possible follow-ups>
  • Re: APL and LISP, Jeffrey Shrager
• Re: Applicable Macros?, Jon L White
• [no subject], Jon L White
• [no subject], MARC at MIT-XX
• [no subject], Deutsch at PARC-MAXC
• Re: Iteration Facilities, Jon L White
  • <Possible follow-ups>
  • Re: iteration facilities, Glenn S. Burke
• Re: Sifting thru the "good mud": LISP vs APL, Jon L White
• Re: Forgot to CC this, Guy . Steele at CMU-10A
• [no subject], Kent M . Pitman
• [no subject], George J . Carrette
• [no subject], George J . Carrette
• Re: Diamonds vs mud?, HGBaker . Symbolics at MIT-Multics
• Re: Diamonds vs Gold, HGBaker . Symbolics at MIT-Multics
• Re: Historical clarification on &PROTECT, Kent M . Pitman
• [no subject], Richard Mark Soley
• [no subject], Earl A . Killian
• Re: I suppose I have to put in my two cents about DEFSUBST, David A . Moon
  • <Possible follow-ups>
  • Re: I suppose I have to put in my two cents about DEFSUBST, Deutsch at PARC-MAXC
  • Re: I suppose I have to put in my two cents about DEFSUBST, George J . Carrette
• Re: LISP vs. APL, Joel Moses
• Re: Snapped Elastic, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Snapped Elastic, Guy . Steele at CMU-10A
• Re: DEFSUBST, Richard M. Stallman
• Re: DEFSUBST clarification, Kent M . Pitman
• Re: LOOP Macro a Winner, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: LOOP Macro a Winner, Guy . Steele at CMU-10A
• Re: LOOP, Carl W . Hoffman
• Re: LOOP loses, Kent M . Pitman
• Re: (more) problems with (STATUS FEATURES), Kent M . Pitman
  • <Possible follow-ups>
  • Re: (more) problems with (STATUS FEATURES), CSVAX . jkf at Berkeley
  • Re: (more) problems with (STATUS FEATURES), Kent M . Pitman
• Re: Moon's proposed incompatible change to PUTPROP, Guy . Steele at CMU-10A
• Re: macro expansion, CSVAX . fateman at Berkeley
  • <Possible follow-ups>
  • Re: macro expansion, Alan Bawden
  • Re: macro expansion, CSVAX . fateman at Berkeley
  • Re: macro expansion, Alan Bawden
  • Re: macro expansion, CSVAX . fateman at Berkeley
  • Re: macro expansion, Alan Bawden
  • Re: macro expansion, Guy . Steele at CMU-10A
• Re: Macros, Bernard S . Greenberg
• Re: Feature double creature, Robert W . Kerns
• Re: FEATURE-CASEQ and TARGET-FEATURES, Kent M . Pitman
• Re: DEFSTRUCT and reclaimable storage, William A. Kornfeld
  • <Possible follow-ups>
  • Re: DEFSTRUCT and reclaimable storage, Daniel L . Weinreb
  • Re: DEFSTRUCT and reclaimable storage, Alan Bawden
• Re: DEFSTRUCT, reclaimable storage, and "resources", William A. Kornfeld
• Re: null LAMBDA bodies?, Jon L White
  • <Possible follow-ups>
  • Re: null LAMBDA bodies?, Daniel L . Weinreb
  • Re: null LAMBDA bodies?, Richard L . Bryan
  • Re: null LAMBDA bodies?, Guy . Steele at CMU-10A
• Re: ((LAMBDA ())) => NIL ?, Kent M . Pitman
• Re: Special names for Open-Coded Functions, Kent M . Pitman
• Re: Open-coding, and proliferation of function names, Jon L White
  • <Possible follow-ups>
  • Re: Open-coding, and proliferation of function names, Kent M . Pitman
  • Re: Open-coding, and proliferation of function names, Guy . Steele at CMU-10A
  • Re: Open-coding, and proliferation of function names, Kent M . Pitman
  • Re: Open-coding, and proliferation of function names, Guy . Steele at CMU-10A
• Re: food for hack., George J . Carrette
  • <Possible follow-ups>
  • Re: food for hack., Richard Mark Soley
• Re: (progn 'compile ...), George J . Carrette
  • <Possible follow-ups>
  • Re: (progn 'compile ...), Earl A . Killian
  • Re: (progn 'compile ...), Robert W . Kerns
• [no subject], Kent M . Pitman
• Re: SUBST, Kent M . Pitman
• Re: PROGN 'COMPILE, Kent M . Pitman
  • <Possible follow-ups>
  • Re: PROGN 'COMPILE, George J . Carrette
• [no subject], Daniel L . Weinreb
• Re: EQ(UAL) in SUBST, Kent M . Pitman
  • <Possible follow-ups>
  • Re: EQ(UAL) in SUBST, Guy . Steele at CMU-10A
  • Re: EQ(UAL) in SUBST, Daniel L . Weinreb
• [no subject], George J . Carrette
• Re: Statistics on Macsyma use of SUBST, Kent M . Pitman
• Re: is it sensible to think of an extended address Lisp for the DEC-20?, HEDRICK at RUTGERS
  • <Possible follow-ups>
  • Re: is it sensible to think of an extended address Lisp for the DEC-20?, Guy . Steele at CMU-10A
  • Re: is it sensible to think of an extended address Lisp for the DEC-20?, Deutsch at PARC-MAXC
  • Re: is it sensible to think of an extended address Lisp for the DEC-20?, Rindfleisch at SUMEX-AIM
  • Re: is it sensible to think of an extended address Lisp for the DEC-20?, Chris Ryland
• Re: is it sensible to think of an extended address Lisp for the DEC-20?, Mark Crispin
• Re: a note on extended addressing lisp for 20's, JoSH
• Re: is it sensible to think of an extended address Lisp for the, Guy . Steele at CMU-10A
• Re: EQP, Kent M . Pitman
  • <Possible follow-ups>
  • Re: EQP, Guy . Steele at CMU-10A
• Re: EQP/EQL, Robert W . Kerns
• Re: EQL, Kent M . Pitman
• [no subject], Robert W . Kerns
• Re: More LOOP fan mail., George J . Carrette
  • <Possible follow-ups>
  • Re: More LOOP fan mail., Guy . Steele at CMU-10A
  • Re: More LOOP fan mail., David Chapman
• Re: LOOP fan mail, Glenn S. Burke
• Re: more loop fan mail, George J . Carrette
  • <Possible follow-ups>
  • Re: more loop fan mail, Edward Barton
• Re: even more loop fan mail, Glenn S . Burke
• Re: LOOP usage, versus "best-optimizeable-codings", Jon L White
• Re: Point of incompatibility between MacLisp and Lispm lisp, William A. Kornfeld
• Re: generalization of PUSH, George J . Carrette
• Re: This really has very little to do with LOOP, Kent M . Pitman
• Re: extended addressing, HEDRICK at RUTGERS
  • <Possible follow-ups>
  • Re: extended addressing, Chris Ryland
  • Re: extended addressing, HEDRICK at RUTGERS
  • Re: extended addressing, Robert W . Kerns
• Re: Add me to mailing list, Martin.Griss
• Re: Is LEXPR-FUNCALL a pain?, George J . Carrette
  • <Possible follow-ups>
  • Re: Is LEXPR-FUNCALL a pain?, Mike McMahon
  • Re: Is LEXPR-FUNCALL a pain?, George J . Carrette
  • Re: Is LEXPR-FUNCALL a pain?, Guy . Steele at CMU-10A
• Re: Consistency: #\... and (FORMAT s "~:C" c), Kent M . Pitman
• Re: Once again a plea for slash, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Once again a plea for slash, Martin.Griss
  • Re: Once again a plea for slash, John G . Aspinall
  • Re: Once again a plea for slash, Deutsch at PARC-MAXC
  • Re: Once again a plea for slash, Daniel L . Weinreb
  • Re: Once again a plea for slash, Howard I . Cannon
  • Re: Once again a plea for slash, CSVAX . fateman at Berkeley
  • Once again a plea for slash, Gerald Jay Sussman
  • Re: Once again a plea for slash, Guy . Steele at CMU-10A
• Re: COPY ?, Jon L White
• Re: COPY-TOP-LEVEL, Jon L White
  • <Possible follow-ups>
  • Re: COPY-TOP-LEVEL, Barry M . Trager
• Re: Misc, Robert W . Kerns
• Re: rationals as a Lisp data type, CSVAX . fateman at Berkeley
  • <Possible follow-ups>
  • Re: rationals as a Lisp data type, George J . Carrette
• Re: Slash: confusing the issue, Daniel L . Weinreb
  • <Possible follow-ups>
  • Re: Slash: confusing the issue, Howard I . Cannon
• Re: Quotation concerning rational arithmetic, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Quotation concerning rational arithmetic, George J . Carrette
  • Re: Quotation concerning rational arithmetic, Guy . Steele at CMU-10A
• Re: Forwarded message and reply, Guy . Steele at CMU-10A
• Re: Division in Smalltalk, Deutsch at PARC-MAXC
• Re: modular arith., George J . Carrette
• Re: Desirable macro, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Desirable macro, Earl A . Killian
  • Re: Desirable macro, Daniel L . Weinreb
  • Re: Desirable macro, Daniel L . Weinreb
  • Re: Desirable macro, Earl A . Killian
• Re: Canonicalization of predicate oredering in DEL, MEM, etc., Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Canonicalization of predicate oredering in DEL, MEM, etc., Daniel L . Weinreb
  • Re: Canonicalization of predicate oredering in DEL, MEM, etc., David A . Moon
• Re: Desirable (?) macro, Guy . Steele at CMU-10A
• Re: default value for GET and friends, Guy . Steele at CMU-10A
• [no subject], Susan Lynn Thunder
• Re: Case study: Macro forms as operators in Maclisp, Kent M . Pitman
  • <Possible follow-ups>
  • Re: Case study: Macro forms as operators in Maclisp, Guy . Steele at CMU-10A
• Re: More on macros in Maclisp, Kent M . Pitman
• Re: even more on macros in maclisp, George J . Carrette
• [no subject], Kent M . Pitman
• [no subject], RMS at MIT-MC
• [no subject], Richard M. Stallman
• Re: Problem with ((FIRST) ...), Richard M. Stallman
  • <Possible follow-ups>
  • Re: Problem with ((FIRST) ...), Kent M . Pitman
• Re: Multiple use of symbols, Richard M. Stallman
• Re: lambda-macros, Kent M . Pitman
• Re: COPYTREE, Kent M . Pitman
  • <Possible follow-ups>
  • Re: COPYTREE, Daniel L. Weinreb
  • Re: COPYTREE, Dave Andre
  • Re: COPYTREE, Guy . Steele at CMU-10A
  • Re: COPYTREE, Carl W . Hoffman
  • Re: COPYTREE, JONL at MIT-MC , RWK at MIT-MC
  • Re: COPYTREE, Daniel L . Weinreb
• Re: Proposed schedule for change from "/" to "\", Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Proposed schedule for change from "/" to "\", Gail Zacharias
  • Re: Proposed schedule for change from "/" to "\", George J . Carrette
  • Re: Proposed schedule for change from "/" to "\", Daniel L . Weinreb
  • Re: Proposed schedule for change from "/" to "\", Guy . Steele at CMU-10A
  • Re: Proposed schedule for change from "/" to "\", George J . Carrette
• Re: \\\\, Kent M . Pitman
• Re: COPYALL, COPYLIST, et alia, Daniel L . Weinreb
  • <Possible follow-ups>
  • Re: COPYALL, COPYLIST, et alia, Dave Andre
  • Re: COPYALL, COPYLIST, et alia, Guy . Steele at CMU-10A
  • Re: COPYALL, COPYLIST, et alia, Chris Ryland
  • Re: COPYALL, COPYLIST, et alia, George J . Carrette
  • Re: COPYALL, COPYLIST, et alia, David A . Moon
  • Re: COPYALL, COPYLIST, et alia, George J . Carrette
  • Re: COPYALL, COPYLIST, et alia, Guy . Steele at CMU-10A
  • Re: COPYALL, COPYLIST, et alia, Daniel L . Weinreb
  • Re: COPYALL, COPYLIST, et alia, Allan C. Wechsler
  • Re: COPYALL, COPYLIST, et alia, Guy . Steele at CMU-10A
• Re: (COP pred form), Kent M . Pitman
• [no subject], Kent M . Pitman
• [no subject], Richard M. Stallman
• [no subject], Dave Andre
• [no subject], Daniel L . Weinreb
• [no subject], Alan Bawden
• Re: / and \, Moon at MIT-AI
  • <Possible follow-ups>
  • Re: / and \, DLW at MIT-AI
  • Re: / and \, Earl A . Killian
  • Re: / and \, Earl A . Killian
  • Re: / and \, Daniel L . Weinreb
• [no subject], Kent M . Pitman
• Re: / to \, Kent M . Pitman
• Re: ``\\ (fixnum gcd) is useless and can simply be flushed'', William G . Dubuque
• [no subject], Richard C. Waters
• [no subject], Richard M. Stallman
• Re: / => \, Alan Bawden
  • <Possible follow-ups>
  • Re: / => \, Henry Lieberman
• Re: FIXNUM-restricted versions of rational funs, Jon L White
• Re: \ and \\, Jon L White
• Re: Proposed change to TRACE, Guy . Steele at CMU-10A
• Re: /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\, David C . Plummer
• Re: /\ vote, Robert W . Kerns
  • <Possible follow-ups>
  • Re: /\ vote, William A. Kornfeld
• Re: /\, Earl A . Killian
  • <Possible follow-ups>
  • Re: /\, George J . Carrette
  • Re: /\, Robert W . Kerns
• Re: /\ Mess., Dave Andre
• Re: /\ Mess, upward compatibility, David A. Moon
  • <Possible follow-ups>
  • Re: /\ Mess, upward compatibility, George J . Carrette
  • Re: /\ Mess, upward compatibility, Dave Andre
• [no subject], Kent M . Pitman
• Re: George, take a walk until your hat floats., Alan Bawden
  • <Possible follow-ups>
  • Re: George, take a walk until your hat floats., George J . Carrette
• Re: George, take a float until your hat walks., Robert W . Kerns
• Re: mode lines, George J . Carrette
  • <Possible follow-ups>
  • Re: mode lines, Kent M . Pitman
  • Re: mode lines, Dave Andre
• Re: file mode lines, Robert W . Kerns
• Re: trace change, Richard C. Waters
• Re: Floating hats, Kent M . Pitman
• Re: ITS getting file properties, Kent M . Pitman
• Re: -*- line, Daniel L. Weinreb
• Re: Explanation about file property lists., Daniel L. Weinreb
• Re: more on file prop lists, Kent M . Pitman
• Re: Compatible? with whom?, Jon L White
  • <Possible follow-ups>
  • Re: Compatible? with whom?, George J . Carrette
• [no subject], George J . Carrette
• Re: Source-to-source transformations, Guy . Steele at CMU-10A
• Re: optimizers, Richard M. Stallman
  • <Possible follow-ups>
  • Re: optimizers, Glenn S . Burke
  • Re: Optimizers, Dick Gabriel
  • Re: optimizers, George J . Carrette
  • Re: Optimizers, Guy . Steele at CMU-10A
  • Re: optimizers, Richard M. Stallman
  • Re: optimizers, George J . Carrette
  • Re: Optimizers, Daniel L. Weinreb
• Re: FILTERs: Source-to-source code transformers, Jon L White
• Re: Use of MULTIPLE-VALUE and VALUES, Jon L White
  • <Possible follow-ups>
  • Re: Use of MULTIPLE-VALUE and VALUES, Glenn S . Burke
  • Re: Use of MULTIPLE-VALUE and VALUES, Glenn S . Burke
  • Re: Use of MULTIPLE-VALUE and VALUES, George J . Carrette
• Re: COMPLR address space, Jon L White
• Re: Optimizers and macros, Daniel L . Weinreb
  • <Possible follow-ups>
  • Re: Optimizers and macros, George J . Carrette
• Re: P.S., regarding optimizers, Daniel L . Weinreb
• Re: Thoughts on GLS's (non)suggestion, Kent M . Pitman
  • <Possible follow-ups>
  • Re: Thoughts on GLS's (non)suggestion, George J . Carrette
• Re: Flush Old I/O symbols in MacLISP?, Jon L White
  • <Possible follow-ups>
  • Re: Flush Old I/O symbols in MacLISP?, Robert W . Kerns
  • Re: Flush Old I/O symbols in MacLISP?, James E . O'Dell
• Re: Compilation in Standard LISP, Martin.Griss
  • <Possible follow-ups>
  • Re: Compilation in Standard LISP, Daniel L . Weinreb
  • Re: Compilation in Standard LISP, Deutsch at PARC-MAXC
• Re: Snide remarks, Richard M . Stallman
• Re: "snide remarks"?, Jon L White
• Re: Filters, Richard M . Stallman
• Re: Idea: New way for optimizers to work, Richard M. Stallman
• Re: Syntax for optimizers in function definition, Richard M. Stallman
• Re: vote on destructuring, Henry Lieberman
  • <Possible follow-ups>
  • Re: Vote on destructuring, Henry Lieberman
• [no subject], Richard M. Stallman
• [no subject], Richard M. Stallman
• Re: upper and lower case, CSVAX . jkf at Berkeley
  • <Possible follow-ups>
  • Re: upper and lower case, George J . Carrette
  • Re: upper and lower case, Howard I . Cannon
  • Re: upper and lower case, Daniel L . Weinreb
  • Re: upper and lower case, CSVAX . jkf at Berkeley
  • Re: upper and lower case, George J . Carrette
  • Re: upper and lower case, Bruce E . Edwards
• [no subject], Kent M . Pitman
• Re: Problem with LETF, Richard M. Stallman
• Re: Case, Richard M. Stallman
• Re: More case, Richard M. Stallman
  • <Possible follow-ups>
  • Re: More case, Earl A . Killian
  • Re: More case, George J . Carrette
  • Re: More case, Earl A . Killian
• Re: DEFMACRO incompatible, Robert W . Kerns
  • <Possible follow-ups>
  • Re: DEFMACRO incompatible, David A. Moon
  • Re: DEFMACRO incompatible, Robert W . Kerns
• Re: Casifying at output time wins for what I want it to do., RMS at MIT-AI
• Re: more on mixed case, CSVAX . jkf at Berkeley
  • <Possible follow-ups>
  • Re: more on mixed case, George J . Carrette
• Re: a quick question about cases, CSVAX . jkf at Berkeley
  • <Possible follow-ups>
  • Re: a quick question about cases, Daniel L . Weinreb
• Re: Question about case, Bruce E. Edwards
• Re: Casifying at output time doesn't win..., Kent M . Pitman
• Re: LET, LETF, etc. What do others think?, Kent M . Pitman
• Re: destructuring, Daniel L . Weinreb
  • <Possible follow-ups>
  • Re: destructuring, George J . Carrette
  • Re: destructuring, Daniel L . Weinreb
  • Re: destructuring, George J . Carrette
• Re: Array modification feature, David L. Andre
  • <Possible follow-ups>
  • Re: Array modification feature, John G . Aspinall
  • Re: Array modification feature, Dave Andre
• Re: [Re: Destructuring syntax], P. David Lebling
• Re: but you're losing flexibility..., Kent M . Pitman
• Re: Old IO symbols in MACSYMA, Jeffrey P . Golden
• Re: Destructuring LET, Kent M . Pitman
• Re: Disappointment, Guy . Steele at CMU-10A
• Re: &keywords, Richard M. Stallman
  • <Possible follow-ups>
  • Re: &keywords, George J . Carrette
  • Re: &keywords, Edward Barton
• [no subject], Kent M . Pitman
• Re: guess what., George J . Carrette
  • <Possible follow-ups>
  • Re: guess what., Barry Margolin
• Re: & as reader syntax, Robert W . Kerns
• Re: Your mail of 3 February 1981 18:37-EST, Barry Margolin
• Re: Oh God! Still More Case!, Robert W . Kerns
• [no subject], Richard M. Stallman
• Re: In search of the compatible DEFMACRO, Jon L White
• Re: Definition Syntax, Bill Long
• [no subject], Jon L White
• [no subject], George J . Carrette
• Re: & as a reader macro., Dave Andre
• Re: New argument-list syntax proposal., Allan C. Wechsler
• Re: Everybody and his brother is a language designer., Allan C. Wechsler
• [no subject], Howard I . Cannon
• Re: (OPTIONAL ...) &RELATED-ISSUES, Kent M . Pitman
  • <Possible follow-ups>
  • Re: (OPTIONAL ...) &RELATED-ISSUES, Glenn S . Burke
• Re: Meta-Flame about flaming: Reply to ACW, Kent M . Pitman
• Re: parsing, Earl A . Killian
• [no subject], Daniel L. Weinreb
• Re: (Spurious argumentation), Bruce E . Edwards
• [no subject], George J . Carrette
• [no subject], Richard M. Stallman
• Re: spurious argumentation., Bruce E . Edwards
  • <Possible follow-ups>
  • Re: spurious argumentation., Robert W . Kerns
  • Re: spurious argumentation., Robert H . Berman
• Re: More concrete remarks on &keywords..., Kent M . Pitman
• Re: Language design online, Jonathan Lettvin
  • <Possible follow-ups>
  • Re: Language design online, Jeffrey Shrager
• Re: symbols and printed representation, George J . Carrette
• [no subject], Kent M . Pitman
• Re: [This reply went to SHRAGE@WHARTON-10], Kent M . Pitman
• Re: [RMS: forwarded], Kent M . Pitman
• Re: Standardization, George J . Carrette
  • <Possible follow-ups>
  • Re: Standardization, Deutsch at PARC-MAXC
  • Re: Standardization, Jeffrey Shrager
• Re: [SHRAGE: Standardization], Kent M . Pitman
• Re: Lisp Compatibility, Lisp differences, Masinter at PARC-MAXC
• [no subject], Richard J . Fateman
• [no subject], Jeffrey P . Golden
• Re: Getting act together on strings, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Getting act together on strings, Daniel L . Weinreb
• Re: SLightly unwarranted flame, Guy . Steele at CMU-10A
• Re: STRING subsequencing functions, etc, Jon L White
• Re: Foot-in-mouth disease, Guy . Steele at CMU-10A
• Re: Fence posts?, Jon L White
• Re: Gronked Quux, Guy . Steele at CMU-10A
• Re: [DWS: LISP info requested], Earl A . Killian
  • <Possible follow-ups>
  • Re: [DWS: LISP info requested], George J . Carrette
  • Re: [DWS: LISP info requested], JWALKER at BBNA
• Re: Z-80 Lisp, Bruce Roberts
• [no subject], CSVAX . fateman at Berkeley
• Re: The utility of readmacros in converting infix expressions., George J . Carrette
  • <Possible follow-ups>
  • Re: The utility of readmacros in converting infix expressions., Jeffrey Shrager
• Re: timings, Charles Frankston
• Re: shrage's APL parsing problems, HGBaker . Symbolics at MIT-Multics
• Re: mouse explanation line in sys 300A, 65.0, Daniel G. Shapiro
• Re: Faculty Positions at Utah, Martin.Griss
• Re: fix,fixr, Richard J . Fateman
• Re: Data-types for "descending" during copying, Jon L White
  • <Possible follow-ups>
  • Re: Data-types for "descending" during copying, Masinter at PARC-MAXC
• Re: LISP security query, Barry Margolin
  • <Possible follow-ups>
  • Re: LISP security query, George J . Carrette
  • Re: LISP security query, Jeffrey Shrager
• Re: lisp security, David A . Moon
  • <Possible follow-ups>
  • Re: lisp security, Deutsch at PARC-MAXC
• Re: Proposed extension to DOLIST, DOTIMES, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Proposed extension to DOLIST, DOTIMES, David A. Moon
  • Re: Proposed extension to DOLIST, DOTIMES, Daniel L . Weinreb
• Re: Return value from DOLIST, DOTIMES, Robert W . Kerns
• Re: DOLIST, with index variable, Jon L White
• Re: Splicing macro's & CGOL., George J . Carrette
  • <Possible follow-ups>
  • Re: Splicing macro's & CGOL., David A . Moon
  • Re: Splicing macro's & CGOL., George J . Carrette
• Re: Splicing macros & CGOL, Jon L White
• Re: Proposed mildly incompatible change to MULTIPLE-VALUE(-BIND), Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Proposed mildly incompatible change to MULTIPLE-VALUE(-BIND), David A . Moon
  • Re: Proposed mildly incompatible change to MULTIPLE-VALUE(-BIND), Jon L White
  • Re: Proposed mildly incompatible change to MULTIPLE-VALUE(-BIND), Guy . Steele at CMU-10A
• Re: maclisp format query, Glenn S . Burke
• Re: New Maclisp mailing lists, Kent M . Pitman
• [no subject], David L . Andre
• [no subject], Daniel L . Weinreb
• [no subject], David L . Andre
• [no subject], Daniel L . Weinreb
• [no subject], David L . Andre
• [no subject], Carl W . Hoffman
• please add me to the mailing list, Bill Vaughan
  • <Possible follow-ups>
  • please add me to the mailing list, Bill Vaughan
• Mailing-list additions, Kent M . Pitman
• Re: Lisp macros, RG
• franz lisp & NIL, Bill Vaughan
• MAILING LIST, STOUTEMYER at UTAH-20
• OPENF, Daniel L . Weinreb
• [no subject], Richard C . Waters
• [no subject], Richard C . Waters
• DICK@ML's #, problems, Kent M . Pitman
• [no subject], JL at MIT-MC
• Found in the Boston Globe, Benson I . Margulies at MIT-Multics
• Intra-dialect Lisp translation, Lars S . Hornfeldt
  • <Possible follow-ups>
  • intra-dialect Lisp translation, Tim Finin
• Destructuring considered harmful, DILL at CMU-20C
• Reply to DESTRUCTURING considered harmfull., George J . Carrette
  • <Possible follow-ups>
  • Reply to DESTRUCTURING considered harmfull., Daniel L . Weinreb
  • Reply to DESTRUCTURING considered harmfull., George J . Carrette
• Reply to reply to DESTRUCTURING C.H., Guy . Steele at CMU-10A
• Variable binding, George J . Carrette
• [no subject], RMS
• [no subject], RMS
• [no subject], Jon L White
• Binding functions vs packages., Richard M . Stallman
  • <Possible follow-ups>
  • Binding functions vs packages., George J . Carrette
• Variable binding discipline, Richard M . Stallman
  • <Possible follow-ups>
  • Re: Variable binding discipline, Guy . Steele at CMU-10A
• LABELS, David A . Moon
• nested function definitions interfering with extensibility., Richard M . Stallman
• NCONC and LAST of locatives, GOSPER at PARC-MAXC
  • <Possible follow-ups>
  • NCONC and LAST of locatives, George J . Carrette
  • NCONC and LAST of locatives, David A . Moon
  • NCONC and LAST of locatives, Daniel L . Weinreb
  • Re: NCONC and LAST of locatives, Guy . Steele at CMU-10A
• Antecedent, what's thy name?, GOSPER at PARC-MAXC
  • <Possible follow-ups>
  • Re: Antecedent, what's thy name?, JoSH
• [no subject], William A . Kornfeld
• Antecedents, Guy . Steele at CMU-10A
• [no subject], Daniel L . Weinreb
• [no subject], David Chapman
• LOGLAN, Guy . Steele at CMU-10A
• more about SEQ, David Chapman
• MACROEXPAND and related functions, Jon L White
• hi-multics is back, Bill Vaughan
• GENLOCAL, Jon L White
  • <Possible follow-ups>
  • GENLOCAL, David A . Moon
• GENSYM/GENTEMP/GENLOCAL, Robert W . Kerns
  • <Possible follow-ups>
  • GENSYM/GENTEMP/GENLOCAL, David A . Moon
• My previous note, Robert W . Kerns
• Why "uninterned" doesn't mean forever, or GENSYMs away!, Jon L White
• GENSYM/GENTEMP, Kent M . Pitman
  • <Possible follow-ups>
  • GENSYM/GENTEMP, Alan Bawden
• GENSYM in MacLisp, Robert W . Kerns
• GEN(whatever), L170DD60
• [no subject], David Chapman
• Lexical variables, Richard M . Stallman
• Suggested new lambda-list syntax, Richard M . Stallman
  • <Possible follow-ups>
  • Suggested new lambda-list syntax, George J . Carrette
  • Re: Suggested new lambda-list syntax, Scott . Fahlman at CMU-10A
  • Suggested new lambda-list syntax, David A . Moon
  • Suggested new lambda-list syntax, Jon L White
  • Re: Suggested new lambda-list syntax, Mark L . Miller
  • Suggested new lambda-list syntax, Mark L . Miller
  • Suggested new lambda-list syntax, Deutsch at PARC-MAXC
• Lambda List Syntax, Bill Long
• Lists for REST, OPTIONAL and AUX look nice, Richard M . Stallman
• [no subject], Richard M . Stallman
• Proposed new lambda-list syntax, David A . Moon
• &NO, Alan Bawden
• About &parsers, Kent M . Pitman
  • <Possible follow-ups>
  • About &parsers, Daniel L . Weinreb
  • About &parsers, George J . Carrette
• implementation of rational numbers, William A . Kornfeld
  • <Possible follow-ups>
  • Re: implementation of rational numbers, Deutsch at PARC-MAXC
  • implementation of rational numbers, Daniel L . Weinreb
• Re: fast gcd, RWG
• rational arithmetic, HGBaker . Symbolics at MIT-Multics
• LAMBDA syntax counter-proposal, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • LAMBDA syntax counter-proposal, Daniel L . Weinreb
  • LAMBDA syntax counter-proposal, David A . Moon
  • Re: LAMBDA syntax counter-proposal, Guy . Steele at CMU-10A
  • LAMBDA syntax counter-proposal, Earl A . Killian
• P.S. to previous message (LAMBDA list counter-proposal), Guy . Steele at CMU-10A
• LAMBDA syntax counter-counter-proposal, Earl A . Killian
• B.S., Guy . Steele at CMU-10A
• LAMBDA proposals and counter-proposals, Kent M . Pitman
  • <Possible follow-ups>
  • LAMBDA proposals and counter-proposals, Earl A . Killian
  • LAMBDA proposals and counter-proposals, Kent M . Pitman
• [no subject], George J . Carrette
• Mary had a moby lambda, Bill Gosper
  • <Possible follow-ups>
  • Mary had a moby lambda, Daniel L . Weinreb
• [no subject], Kent M . Pitman
• Forwarding lost copy of mail from BENSON, Guy . Steele at CMU-10A
• LAMBDA extension, Masinter at PARC-MAXC
• NIL LET., George J . Carrette
• [no subject], George J . Carrette
• History of Lisp macros, Alan Bawden
  • <Possible follow-ups>
  • Re: History of Lisp macros, Deutsch at PARC-MAXC
• [no subject], Richard M . Stallman
• Macros in Interlisp, MASINTER at PARC-MAXC
  • <Possible follow-ups>
  • macros in Interlisp, Masinter at PARC-MAXC
• [no subject], Richard M . Stallman
• InterLISP Macros, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: InterLISP Macros, Masinter at PARC-MAXC
  • InterLISP Macros, Guy . Steele at CMU-10A
• [no subject], Kent M . Pitman
• [no subject], Eric Benson
• "Until you try to implement it", Richard M . Stallman
  • <Possible follow-ups>
  • Re: "Until you try to implement it", Eric Benson
• [no subject], George J . Carrette
• c*r, John Foderaro
  • <Possible follow-ups>
  • c*r, George J . Carrette
  • C*R, Guy . Steele at CMU-10A
  • c*r, Kim . jkf at Berkeley
  • Re: c*r, CSVAX . fateman at Berkeley
  • C*R, Guy . Steele at CMU-10A
  • Re: C*R, Kim . jkf at Berkeley
  • c*r, John Foderaro
  • c*r, George J . Carrette
• More pointless hot air about cdaddaddaadddaadaaddddaaar, Alan Bawden
• CDDADADADADADADAAADADADADAR, Allan C . Wechsler
• a lisp without cons is not like a day without sunshine, CSVAX . fateman at Berkeley
• A day without sunshine, Guy . Steele at CMU-10A
• [no subject], Kent M . Pitman
• Query, Alan Bawden
  • <Possible follow-ups>
  • Re: Query, John Foderaro
• C*R and language design, Guy . Steele at CMU-10A
• CR, Kim . fateman at Berkeley
  • <Possible follow-ups>
  • Re: CR, VaughanW . REFLECS at HI-Multics
• [no subject], Jeffrey P . Golden
• [no subject], Richard M . Stallman
• Multiple-valued SQRT, Guy . Steele at CMU-10A
  • <Possible follow-ups>
  • Re: Multiple-valued SQRT, CSVAX . fateman at Berkeley
• C*R improvement, Scott . Fahlman at CMU-10A
• More Lisp History Trivia Quiz, Masinter at PARC-MAXC
  • <Possible follow-ups>
  • More Lisp History Trivia Quiz, George J . Carrette
• Tail Recursion, Dick Gabriel
  • <Possible follow-ups>
  • Re: Tail Recursion, Tony Hearn
• backquote query, Don Morrison
  • <Possible follow-ups>
  • backquote query, Robert W . Kerns
  • backquote query, Robert W . Kerns
• backquote trivia, for you history fans., George J . Carrette
• Backquote depth, Guy . Steele at CMU-10A
• clarification regarding backquote query, Don Morrison
• 'backquote' actions, Jon L White
• minilisp, JoSH
  • <Possible follow-ups>
  • Re: minilisp, kwh
• Interlisp and MacLisp, 2Lt Eric J . Swenson
• Two little suggestions for macroexpansion, Jon L White
  • <Possible follow-ups>
  • Two little suggestions for macroexpansion, David A . Moon
  • Re: Two little suggestions for macroexpansion, Fahlman at CMU-20C
• Those two little suggestions for macroexpansion, Kent M . Pitman
• Comparison of "lambda-macros" and my "Two little suggestions ...", Jon L White
• The format ((MACRO . f) ...), Jon L White
• Incredible co-incidence about the format ((MACRO . f) ...), Jon L White
  • <Possible follow-ups>
  • Incredible co-incidence about the format ((MACRO . f) ...), HIC at SCRC-TENEX
• Interlisp and MacLisp (almost), 2Lt Eric J . Swenson
  • <Possible follow-ups>
  • Interlisp and MacLisp (almost), Tim Finin
• &mumbles at all levels., Alan Bawden
  • <Possible follow-ups>
  • &mumbles at all levels., David L . Andre
  • &mumbles at all levels., George J . Carrette
• Re: &mumbles at all levels -- BIND-ARGS, JonL at PARC-MAXC
• UNLESS -- or something like it., Robert P . Krajewski
  • <Possible follow-ups>
  • Re: UNLESS -- or something like it., John Foderaro
• LOOP CONTINUE STATEMENT, Matt BenDaniel
  • <Possible follow-ups>
  • LOOP CONTINUE STATEMENT, MOON at SCRC-TENEX
  • LOOP CONTINUE STATEMENT, Matt BenDaniel
• Call For Papers, Bill Vaughan
• function cells, Julian Padget
  • <Possible follow-ups>
  • Re: function cells, Deutsch . PA
  • Re: function cells, Bobrow . PA
  • Function cells, TIM
    • Re: Function cells, Bobrow . PA
  • Re: Function cells, Eric Benson
  • Re: Function cells, Deutsch . PA
  • Re: Function cells, Julian Padget
  • Re: Function cells, Bobrow . PA
  • Function cells, ZVONA
    • Function cells, Robert W . Kerns
  • Function cells, David A . Moon
  • Function cells, ZVONA
  • Re: Function cells, John Foderaro
  • Re: Function cells, Julian Padget
• Function cells., George J . Carrette
• Zippy the mailer, or ... are we on the net yet?, George J . Carrette
• Administrative Note, Kent M . Pitman
• Function Cells -- the history, JonL . pa
• your note on Function Cells., George J . Carrette
• Addition to list, SAE-ADA
• Backquote history, MASINTER . PA
  • <Possible follow-ups>
  • Backquote history, Alan Bawden
  • Backquote history, Kent M Pitman
  • Re: Backquote history, masinter . pa
  • Backquote history, Allan C. Wechsler
  • Backquote history, Alan Bawden
• [GJS: Backquote history], Kent M Pitman
• Backquote, Drew McDermott
• History of "backquote" macro, JONL . PA
• eval-while-possible, Christopher Fry
• where to donate cans????, Michael J . Beckerle
• Info request: Microcomputer file transfer protocols for PC & UNIX, Daniel C . Cheng
• mail list addition, LCG . GREEN
• [MJackson.Wbst: Why Your Pascal and Modula-2 Programs Don't Work], JonL . pa
• Benchmark - PERQ CL vs Apollo T, Skef Wholey
  • <Possible follow-ups>
  • Benchmark - PERQ CL vs Apollo T, Charles Dolan
• Concept-LNZ manual, Michael M . How
• IBM PC Software Development Positions Available, Daniel C . Cheng
• UCLA Perq, Joseph . Ginder
• Tomos Moped, Michael J . Beckerle
• televideo terminal help, DShevitz
• 6871 partners wanted, Michael J . Beckerle
• defsubst in Maclisp, Barry Margolin
  • defsubst in Maclisp, Kent M Pitman
• Modem help!, Michael D. O'Keefe
• Berkeley Apartment to let for July, Steve Heller
• Graduation tickets for Sale, Johnathan Devine
• [no subject], Ben Moreland
• I have a car..., leifer
• telescope drive equipment for sale, Mark L. Lambert
• Expert System / Graphics Opportunities Available, Steve Heller
• [no subject], Communications Satellite
• Scheme availability, on ERCC DEC-10
• Lost Notebook, John T. Maeda
• 68000 kit, David C . Anderson
• Tae Kwon Do Demonstration, Steve Heller
• Availbility of Kana font., Robert H . Kassel
• (TRACE q1 q2 ... ) patterns, Harold Carr
• Spring Dance, Gays at MIT
• Re: I agree that it should not be as rigidly defined as APL, Jeffrey Shrager
• Re: LISP machine diamonds, Jeffrey Shrager
• Re: control vs constraint, Jeffrey Shrager
• [no subject], Jeffrey Shrager
• Re: An amusing sidenote to the kwote controversy:, Jeffrey Shrager
• [no subject], Unknown
• Lisp for PR1ME needed, Steve Platt
• Opps -- that's LET (I've been told) -- "never mind", Jeffrey Shrager
• Avoiding recomputation or recapitulation: (g x x), Jeffrey Shrager
• interlisp-like primitives in lisp, Steve Platt