Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!think!husc6!bu-cs!bzs
From: bzs@bu-cs.BU.EDU (Barry Shein)
Newsgroups: net.lang.lisp
Subject: Re: Franz Lisp compiler problems
Message-ID: <1661@bu-cs.bu-cs.BU.EDU>
Date: Fri, 3-Oct-86 17:04:32 EDT
Article-I.D.: bu-cs.1661
Posted: Fri Oct  3 17:04:32 1986
Date-Received: Sat, 4-Oct-86 12:15:35 EDT
Organization: Boston U. Comp. Sci.
Lines: 31


Re: recommendation to use #+Franz

I agree, it's the right answer to the question, but I just had a
fun experience with something like that.

I was writing a piece of code which would run equivalently on both
Franz and Common lisp. To separate out the things I needed to attain
compatibility I put two sections at the top, one #+Franz and the other
#+Common.

One of the common lisp statements used a #\c, franz could not
read this and broke on the statement it was trying to ignore.

My only point is, the feature is handy, but it still leaves something
to be desired. I think the C-preprocessor, using only textual
substitutions, still has some advantages, perhaps a cross like:

#{ (arbitrary sexpr)

#}

A la the C pre-processor would be helpful, where the rule is if the
statement evals to nil the lisp reader does read-lines until the
#} is seen, rather than trying to do a (read) and throwing that
away, which will fire up readmacros.

Anyhow, a word to the wise...(btw, this is in no way a problem peculiar
to franz lisp.)

	-Barry Shein, Boston University