Brett Cannon wrote: > On 8/2/05, Phillip J. Eby <pje at telecommunity.com> wrote: >>It seems to me that multiple inheritance is definitely the right idea, >>though. That way, we can get the hierarchy we really want with only a >>minimum of boilerplate in pre-3.0 to make it actually work. > > Yeah. I think name aliasing and multiple inheritance will take us a > long way. Warnings should be able to take us the rest of the way. > > -Brett (who is still waiting for a number; Barry, David, you out there?) And it will let us get rid of some of the ugliness in my v 0.1 proposal, too (like Error being a child of StandardError, instead of the other way around). Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia --------------------------------------------------------------- http://boredomandlaziness.blogspot.com
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4