Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!rutgers!aramis.rutgers.edu!bearcat.rutgers.edu!lou From: lou@bearcat.rutgers.edu (Lou Steinberg) Newsgroups: comp.lang.lisp Subject: Re: LISP compiler? Message-ID: Date: 13 Nov 89 22:00:00 GMT References: <5081@internal.Apple.COM> <5031@tekcrl.LABS.TEK.COM> <5140@internal.Apple.COM> <1989Nov10.154943.18376@hellgate.utah.edu> <31645@news.Think.COM> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 20 Cc: lou In article <31645@news.Think.COM> barmar@leander.think.com (Barry Margolin) writes: > Functions that take functional arguments will accept either a > function or a symbol (automatically calling SYMBOL-FUNCTION on the latter); > they will no longer take lambda lists. You still have to be sure somehow that the user hasn't consed up a runtime list and used setf of symbol-definition to store it as the definition of some symbol. (By the way, as at least one poster has pointed out, in my original message when I spoke about "lambda expressions" causing problems, what I meant was "lists consed up at runtime being used as function definitions". My sloppy wording appears to have confused several people, for which I apologize.) -- Lou Steinberg uucp: {pretty much any major site}!rutgers!aramis.rutgers.edu!lou arpa: lou@cs.rutgers.edu