Scribit Jonathan S. Shapiro dies 27/03/2008 hora 15:34:
> We have an open issue concerning initializer expressions. At the
> moment, we permit arbitrary expressions. This can lead to forward
> reference issues and also to non-terminating initializers.

Is it really an issue to let the user shoot himself in the foot? Are the
problematic cases detectable? Could it be an option for the compiler?

I'd be happy if I could switch to any of:

- let me do what I want and shut up
- give me a warning when I use any non provably safe forms
- give me a fatal error when I use any non provably safe forms

Note that I have a bias here: I like Common Lisp partly because the
whole expressive power of the language is available both at compile time
as well as run time.

And there are quite nasty corner cases with expressions evaluated at
compile time to be used at run time, and many ways to screw up
unexpectedly.

Optionnaly,
Pierre
-- 
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A

Attachment: signature.asc
Description: Digital signature

_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to