Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!boulder!sunybcs!rutgers!ucla-cs!zen!ucbvax!SCORE.STANFORD.EDU!ALDERSON
From: ALDERSON@SCORE.STANFORD.EDU (Rich Alderson)
Newsgroups: comp.ai.digest
Subject: Lisp Syntax
Message-ID: <12335379020.33.ALDERSON@Score.Stanford.EDU>
Date: Thu, 17-Sep-87 13:40:44 EDT
Article-I.D.: Score.12335379020.33.ALDERSON
Posted: Thu Sep 17 13:40:44 1987
Date-Received: Wed, 23-Sep-87 06:43:34 EDT
References: <AIList-REQUEST@SRI.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 33
Approved: ailist@stripe.sri.com

In AIList V5 #213, we find:

    Date: 14 Sep 87 04:25:10 GMT
    From: mtune!codas!killer!usl!elg@RUTGERS.EDU  (Eric Lee Green)
    Subject: procedures and data

    ...
    When procedure symbols are encountered in the eval stream, they are called
    with the next list in the eval stream as the parameter list.  A special
    prefix character is necessary to explicitly access the procedure-object,
    to, for example, assign it to another variable.

    A program might look like

    + (2 2)
    print ( / (2 f))

Without commenting on the questions raised, I'd just like to point out that the
proposed syntax is "eval-quote" Lisp (as opposed to "eval" Lisp) extended to
non-top-level forms.  An "eval-quote" Lisp, such as Lisp 1.5, is one in which
the top-level loop is defined in Lisp as

	(defun top-level-loop ()
	   loop-top
	   (print (apply (read) (read)))
	   (go loop-top))

(NB:  This is typical Lisp 1.5 programming style--"let" and friends didn't yet
exist.)

Rich Alderson
alderson@score.stanford.edu
-------