Re: [Pyobjc-dev] AppKit vs. import *
Brought to you by:
ronaldoussoren
From: Bob I. <bo...@re...> - 2005-05-30 05:36:03
|
On May 29, 2005, at 10:22 PM, Ronald Oussoren wrote: > > On 30-mei-2005, at 5:11, Bob Ippolito wrote: > > >> >> On May 29, 2005, at 5:11 PM, Bill Bumgarner wrote: >> >> >> >>> On May 29, 2005, at 4:30 PM, Bob Ippolito wrote: >>> >>> >>> >>>> Yeah, but what next? Filtering the class list sounds like a >>>> nearly worthless task. The namespace is already quite polluted, >>>> and it's *flat*. It can only really be in one place. >>>> >>>> >>>> >>> >>> In this case, we do have a very hard line in the sand. >>> >>> Filter all classes/symbols from the NeXTSTEP 3.3 runtime that >>> have been deprecated for the last decade, but still appear >>> because of god knows what esoteric backwards compatibility need >>> that may not have existed for about 5 years anyway. >>> >>> It looks like the list is limited to List, Object, and Protocol. >>> At least, that is all that is found in the public headers. >>> Goodness knows what might be in the runtime that isn't advertised >>> in the header. >>> >>> >> >> Protocol is still used in the runtime, and it inherits from Object. >> >> So you still think it's a good idea to add junk to PyObjC to >> filter out two class names (HashTable and List)? >> > > I think it's a good idea to filter all 4 of them in loadBundle and > only there. objc.lookUpClass('Object') should still work. I really don't see the point. -bob |