From: Brian M. <bma...@cs...> - 2005-03-05 00:28:29
|
On Mar 4, 2005, at 4:03 AM, Nikodemus Siivola wrote: > On Wed, 2 Mar 2005, Brian Mastenbrook wrote: > >>> * Remove binding for SB-C::*POLICY* from LOAD. However, since this >>> means >>> that third-party code can eg. globally set (SAFETY 0), make top >>> level >>> OPTIMIZE declarations signal style-warnings under LOAD, and add >>> information >>> about changed policy to :VERBOSE output from LOAD. >>> Thereafter current file-local effect could be achived with >>> (eval-when (:compile-toplevel) (proclaim ...)) >> >> I'll throw my two cents in: I think #1 and #2 are great ideas, but #3 >> is a terrible idea just as a matter of user expectation. There is >> quite a lot of source out there that does (declaim (optimize ...)), >> and we're not gaining anything wrt ANSI by breaking the expectation >> that this only effects file scope. > > I understand and somwhat agree with the sentiment, but I'm also at a > loss to find any justification for file-level policies in CLHS. Hm. After a reading of the relevant sections, I concede that the load-time effect of declaim should not be file-local. (The compile-time effect is allowed to be, from what I can tell, and this may still be worthwhile.) Your suggestion makes more sense to me now. -- Brian Mastenbrook bma...@cs... http://cs.indiana.edu/~bmastenb/ |