Re: Should undefined behavior be encouraged in Emacs?

[Stefan Monnier]

> I don't know about convenient error-*handling*, but if Stefan wants to
> prevent people from using the value of primitives called only for

This is Elisp we're talking about: no types, no "preventing people".
There's only positive/negative encouragement.

> side-effects, he can always provide "convenient error generation" by
> having such primitives return Qunbound (or whatever it's called in

If the Qunbound value escapes to Elisp I'm sure we'll get bug reports.


        Stefan