News for hackers. Stuff that matters.
Re:What is the best way to solve an Objective-C namespace co... by aufreak3 on Sunday May 20, 2012 @05:43AM (#3998396)
This is interesting, but doing it all at the compiler and language level seems like overkill. ObjC is a dynamic language, so the important thing is to have namespacing support in the runtime. If the user of a framework or bundle can specify a (reified) namespace to load a bundle's classes/protocols/etc and the runtime and language support A.B.C style class and protocol names, that might be enough to solve name collision problems. The framework/bundle author need not then bother to find a suitable globally unique name. This would certainly be enough to solve the original poster's problem.

I'm not sure I've thought through all issues with the above approach, but the whole @namespace thing seems gross overkill to me.

There are no comments on this comment yet.