Guido van Rossum wrote: > It is possible to compromise the integrity of a built-in type by > subclassing it if the type wasn't carefully written to expect > subclassing.
Disallowing subclassing in Python may make sense, but it seems unreasonable not to allow subclassing by consenting C code that is careful not to compromise any integrity. Maybe there should be two flags for this instead of just one? -- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | Carpe post meridiem! | Christchurch, New Zealand | (I'm not a morning person.) | [EMAIL PROTECTED] +--------------------------------------+ _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
