[elephant-devel] Pure-Lisp memutil?

[Ian Eslick]

Can you expand on your thinking as to why the user may want to turn  
off optimizations and by what mechanism you would suggest doing  
that?  For production use the optimizations make sense.  If you are  
conservative I think many lisps allow you to override the inlined  
declarations and limit the maximum and minimum value of optimization  
settings.  If not, you can always evaluate things instead of  
compiling them for debugging or making sure the problem isn't in the  
library.

In theory recent releases should be well tested and debugged,  
especially the paths through serialization, memutil and the slot  
protocol; they're speed critical so it's reasonable to run them fast  
and you can always turn that off by the above methods.

Just my thinking on the subject!

Ian

On Nov 20, 2006, at 5:53 PM, Pierre THIERRY wrote:

> Scribit Ian Eslick dies 20/11/2006 hora 10:04:
>> Reading through memutil.lisp should give you a feel for some of the
>> design tradeoffs...
>
> I'm surprised in memutil.lisp by the optimize declarations. In the  
> slot
> protocol also, there are some declarations for maximum speed, and here
> for minimum safety also. I'm not sure if it wouldn't be best to let  
> the
> user choose.
>
> In a same vein, I may have a working Debian package by the end of the
> night, and I replaced -O3 in the Makefile by $(CFLAGS). I'm not  
> sure but
> it may be a strong recommandation in Debian.
>
> Curiously,
> Pierre
> -- 
> nowhere.man at levallois.eu.org
> OpenPGP 0xD9D50D8A
> _______________________________________________
> elephant-devel site list
> elephant-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/elephant-devel