Movatterモバイル変換

Re: packages, lexical variables, and compiling

• To:DCP@SCRC-QUABBIN.ARPA
• Subject: Re: packages, lexical variables, and compiling
• From:Gregor.pa@Xerox.COM
• Date: Thu, 03 Apr 1986 14:32:00 -0000
• Cc:smh@MIT-EMS.ARPA,greek%bach.decnet@hudson.dec.com,common-lisp@SU-AI.ARPA
• In-reply-to: David C. Plummer <DCP@SCRC-QUABBIN.ARPA>'s message of Thu, 3 Apr 86 11:58 EST

I think there are two answers to "Haflich's little program".Answer 1:Any program that depends on the order that various symbols are internedto work correctly should do so explicitly.  At the beginning of theprogram there should be all the make-packages, shadows and lists ofsymbols to be interned in the correct order.To depend on the order that various symbols are loaded implicitly (i.e.by depending on the order in which functions which use those symbols areloaded) is just asking for trouble.Answer 2:Programmers should be allowed to assume that "as much as is possible"loading a compiled file and loading the source file have the sameeffect.I guess I believe both of these answers, and so I think CLtL shouldrequire that the symbols be interned.  But I can't think of a reasonablecoding style that would *really* depend on this feature.P.S.   Option 2, "CLtL requires that the symbols not be created",clearly doesn't make any sense at all for all the reasons mentioned byDCP and other reasons as well.

• Prev by Date:internal symbol preservation
• Next by Date:[JAR@MC.LCS.MIT.EDU: changes]
• Previous by thread:packages, lexical variables, and compiling
• Next by thread:Lexical variables and compilation.
• Index(es):
  • Date
  • Thread