[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [spr4709] Some system code apparently calls WARNING, not a defined function?

To: cox@franz.com
Subject: Re: [spr4709] Some system code apparently calls WARNING, not a defined function?
From: cox@franz.com (Charles A. Cox)
Date: Thu, 12 Dec 1991 23:58:55 -0500
Bh: append spr4709
Bh-id: spr4709
Cc: mitchell@gargoyle.uchicago.edu, Allegro-CL@ucbvax.berkeley.edu, bugs@franz.com, mitchell@gargoyle.uchicago.edu, techstaff@gargoyle.uchicago.edu, converse@gargoyle.uchicago.edu, berger@gargoyle.uchicago.edu
Class: bh
In-reply-to: Charles A. Cox's message of Thu, 12 Dec 91 17:59:04 PST <9112130159.AA06907@crisp.Franz.COM>

>   The reason is that Common Lisp implementations represent a lexical
> environment differently when it is compiled from when it is
> interpreted.

  There is a small typo in the above sentence from my last note I want
to correct.  I meant to say

 ... Common Lisp implementations can represent a lexical ...
                                 ^^^
	Charley

References:
- Re: [spr4709] Some system code apparently calls WARNING, not a defined function?
  - From: cox@franz.com (Charles A. Cox)

Prev by Date: Re: [spr4709] Some system code apparently calls WARNING, not a defined function?
Next by Date: Why does #s(foo :bar baz) cause error in ACL?
Previous by thread: Re: [spr4709] Some system code apparently calls WARNING, not a defined function?
Next by thread: Why does #s(foo :bar baz) cause error in ACL?
Index(es):
- Date
- Thread