Comment 3 for bug 1429520
Revision history for this message
| Christophe Rhodes (csr21-cantab) wrote Re: [Bug 1429520] Re: set-pprint-dispatch on nonexistent type causes maximum error depth excession | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Douglas Katzman <email address hidden> writes:
> But really I think we should just refuse to install the dispatch
> entry, because while it is not undefined per se, it is pretty clear
> that it will lead to prohibited behavior: TYPEP says "The consequences
> are undefined if the type-specifier is not a type specifier." And the
> behavior of the pprint-dispatch is more-or-less to invoke TYPEP
> although it doesn't say that in those words.
I could live with that, but we still need to handle errors from running
TYPEP, because of the possibility of users handing us (SATISFIES ...)
types where the predicate signals an error.
Christophe