[Python-Dev] Re: PEP 246: LiskovViolation as a name (original) (raw)
David Ascher DavidA at ActiveState.com
Wed Jan 12 00:21:29 CET 2005
- Previous message: [Python-Dev] Re: PEP 246: LiskovViolation as a name
- Next message: [Python-Dev] Re: PEP 246: LiskovViolation as a name
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guido van Rossum wrote:
My point is that it'd be nice if we could come up with an exception name which could be grokkable without requiring 1) Google, 2) relatively high-level understanding of type theory.
How about SubstitutabilityError?
That would be far, far better, yes.
We did that for UnboundLocalError, which subclasses NameError. Perhaps we can rename NameError to UnboundVariableError (and add NameError as an alias for b/w compat).
Sure, although (and here I'm pushing it, I know, and I should have argued it way back then), the notion of 'unbound' is possibly too low-level still. 'Unknown' would probably carry much more meaning to those people who most need it.
But yes, you're catching my drift.
--david
- Previous message: [Python-Dev] Re: PEP 246: LiskovViolation as a name
- Next message: [Python-Dev] Re: PEP 246: LiskovViolation as a name
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]