I'm hesitant to agree to namespaces, on the basis that I don't want line 4 to significantly impact what line 400 does. With import/include and prefixing, the code either compiles or it doesn't. With namespaces, you run the risk of getting one class when you're thinking of another.
The other issue is that I don't know how namespaces could avoid conflicts of a messages. That is, if someone category-extended an NSObject when they made it for 10.4, and in 10.5, a message with that name comes out, bad things happen.
In the meantime, frameworks (with recursive frameworks, at that) and the use of a 2 or 3 letter prefix has been holding up rather well.
by Blain — Oct 01
The other issue is that I don't know how namespaces could avoid conflicts of a messages. That is, if someone category-extended an NSObject when they made it for 10.4, and in 10.5, a message with that name comes out, bad things happen.
In the meantime, frameworks (with recursive frameworks, at that) and the use of a 2 or 3 letter prefix has been holding up rather well.