Edward C. Jones wrote:
> I suggest a singleton object "UseForbidden" ("Py_UseForbidden" in C).
It should be called "Mu". :-)
Although such an object could cause a lot of pain to
debuggers and other such introspective code.
Actually this sounds a lot like a signaling Not-a-number (sNaN) from IEEE754. One can pass around a sNaN, but any use will raise a (numeric) exception. Similarly, you want a signaling Not-an-Object (sNaO) that also doesn't like to be passed as a function argument. It is the last bit that makes it a pain, since what if your function is log_error_value(sNaO)?
-Kevin
_______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
