News for hackers. Stuff that matters.
Re:What is the best way to solve an Objective-C namespace co... by barumrho on Saturday May 19, 2012 @11:56PM (#3997889)
This file seems to do the trick. Using macros to override class names. https://github.com/jverkoey/nimbus/blob/master/src/core/src/...
Re:What is the best way to solve an Objective-C namespace co... by buddydvd on Sunday May 20, 2012 @02:18AM (#3998098)
The framework is divided into modules. For each module you include in your static lib (even the ones that gets added indirectly), you need to add its namespace header file. The file you linked to is the namespace header for the Core module. There are more.

Perhaps this could be avoided by just replacing all class names with macros (e.g. _N(NILinkedList)), though that might hinder code completion.

Re:What is the best way to solve an Objective-C namespace co... by pooriaazimi on Sunday May 20, 2012 @08:51AM (#3998642)
I'm getting more confused. Using #if... requires recompilation, doesn't it? So how can a library use them?

Now that I think about it, I see that I don't have any idea how 'dylib's work... I should look them up.

Re:What is the best way to solve an Objective-C namespace co... by buddydvd on Sunday May 20, 2012 @03:43PM (#3999830)
If you are building your own static library and would like to distribute Nimbus with it, this feature allows you to add a prefix to all Nimbus classes without having you to manually rename them. This lets users of your static lib free to include Nimbus with their project without triggering a name conflict with the one included with your lib.