<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">My two cents. Let's absolutely positively not have namespace for objective-c.<div><br></div><div>1. Somehow c has survived 30+ years not needing namespaces. I am told that it is not on the table yet.</div><div> When, and if, namespaces appear for c, it can extend to objc as needed.</div><div>2. For objective-c++, make objective-c live, and thrive, using c++'s namespace.</div><div><br></div><div><br></div><div>- fariborz</div><div><br></div><div><div><div>On Nov 11, 2010, at 8:34 AM, Owen Shepherd wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 11 Nov 2010, at 13:37, Ariel V Feinerman wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Everyone strongly discourages the use "using namespace" since the objects from tens used namespaces can clashes, well then to make short namespace names we can use aliases, but would they clash like prefixes? <div>
<br></div></blockquote><div><br></div><div>Indeed, though there are other useful uses of it (e.g. before C++0x's "inline namespaces" support, I have used it in order to give binary incompatible versions of a library different symbols). It is also perfectly acceptable for the library implementer to do</div><font class="Apple-style-span" color="#006312"><br></font></div></div></blockquote></div><br></div></body></html>