You should be able to make "standard_error_message"s that
do not generate secondary errors.
If you fail, a crude minimal error handling should be okay
as a last resort.
The Lisp system on Symbolics had both. It had a too-many-error-frame
detector for the error reporter that used a crude system when
triggered. It would be nice that the crude error messages be settable
in a way that is hardended, perhaps env vars?
Zope maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -