[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Hvatum@MIT-MULTICS.ARPA, barmar@Think.COM
- Subject: Compiling CASE
- From: Don Morrison <dfm@JASPER.PALLADIAN.COM>
- Date: Tue, 14 Apr 87 16:32 EDT
- Cc: common-lisp@SAIL.STANFORD.EDU
- In-reply-to: <870411100755.599053@MIT-MULTICS.ARPA>
- Reply-to: Don Morrison <DFM%JASPER@LIVE-OAK.LCS.MIT.EDU>
Date: Sat, 11 Apr 87 06:07 EDT
To Don Morrison: What is the meaning of declaring a MACRO NOTINLINE?
CLtL doesn't imply that this is even possible.
(Which is not to say that CLtL implies that it ISN'T possible - I'm
being very careful with my wording here.)
You and barmar are right; my brain was turned off. Notinline has nothing to do with
it. Sorry about that.
Date: Fri, 10 Apr 87 12:58 EDT
From: Barry Margolin <barmar@Think.COM>
Date: Wed, 8 Apr 87 10:37 EDT
From: Don Morrison <firstname.lastname@example.org>
I wonder, however, if all implementations do the right thing if you declare a macro
which is treated specially as notinline?
I don't think it should be necessary to declare/proclaim a macro
notinline. For the macro to work at all, the defmacro must be seen by
the compiler before it tries to compile the use of the macro. I would
hope that the macro would be smart enough to notice that the user has
overridden the default definition.