From: Brian M. <bma...@cs...> - 2005-03-03 01:04:19
|
On Mar 1, 2005, at 3:05 AM, Nikodemus Siivola wrote: > * Remove the separate interactive policy, as it only serves to > confuse. > > * Process initialization files with READ & EVAL, not LOAD, so that > global policies, startup package, etc. can be modified by them. > > * 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. -- Brian Mastenbrook bma...@cs... http://cs.indiana.edu/~bmastenb/ |