Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ll-xn!mit-amt!mit-eddie!barmar
From: barmar@mit-eddie.MIT.EDU (Barry Margolin)
Newsgroups: net.lang.lisp
Subject: Re: Franz Lisp compiler problems
Message-ID: <3385@mit-eddie.MIT.EDU>
Date: Sun, 5-Oct-86 03:40:45 EDT
Article-I.D.: mit-eddi.3385
Posted: Sun Oct  5 03:40:45 1986
Date-Received: Tue, 7-Oct-86 19:57:35 EDT
References: <3542@umcp-cs.UUCP> <708@bcsaic.UUCP>
Reply-To: barmar@mit-eddie.UUCP (Barry Margolin)
Organization: MIT, EE/CS Computer Facilities, Cambridge, MA
Lines: 23
Keywords: macros

In article <708@bcsaic.UUCP> michaelm@bcsaic.UUCP (michael maxwell) writes:
>In article <3542@umcp-cs.UUCP> dsn@umcp-cs.UUCP (Dana S. Nau) writes:
>>I'm trying to get Franz Lisp to compile macros without putting
>>	(declare (macros t))
>>in the file being compiled.
...
>>I thought this could be done by invoking the compiler as follows:
>>	liszt -e '(declare (macros t))' foo.l
>>However, this didn't work ...
>I'm not sure why this didn't work;....

I think I am.  He should have used 
	liszt -e '(macros t)' foo.l

If Franz declare is like Maclisp declare, it means that the enclosed
forms should be evaluated when the form is compiled; when a declare form
is evaluated by the interpreter it is ignored completely.  So, the
original version passed in a declare form, which was evaluated (not
compiled) and summarily ignored.
-- 
    Barry Margolin
    ARPA: barmar@MIT-Multics
    UUCP: ..!genrad!mit-eddie!barmar