4 ms·
Apple is now suggesting that you use three-character class name prefixes, since they claim all the two character ones. So you saw that talk at WWDC as well? Ev
by Zev 16y ago
Apple is now suggesting that you use three-character class name prefixes, since they claim all the two character ones.
So you saw that talk at WWDC as well? Every engineer from Apple that I've spoken to and asked about this has gone "What?! Did he really say that? Ignore it. We don't recommend that. Not at all."
Seeing as you're writing ObjC using a compiler I've worked on, I think that probably understand the "low level shit" better than you do.
You work on LLVM? Props to you, if so. Thats an awesome project. However, if you work on gcc, I haven't used that in over a year :-)
(I kid. Props to you, either way. I can't do what I do without what you do.)
- ant5 16y agoSo you saw that talk at WWDC as well? Every engineer from Apple that I've spoken to and asked about this has gone "What?! Did he really say that? Ignore it. We don't recommend that. Not at all." Regardless of what they say, Apple is still claiming new two-character prefixes, including the one I've been using for years. You work on LLVM? Props to you, if so. Thats an awesome project. However, if you work on gcc, I haven't used that in over a year :-) I'm a big fan of LLVM, but no, I've done nothing with it. That said, if you're using clang for your production builds, you're a much braver soul than me. There are still plenty of codegen issues, especially in the new iPhone/ARM support. There's a reason Apple is still using GCC.
- Zev 16y agoThat said, if you're using clang for your production builds, you're a much braver soul than me. Hardly brave; I only use it personal projects (which target 10.6/64-bit Mac) and debug builds. Release/Ad Hoc/Distribution builds for what I work on uses llvm-gcc. But, I'm not responsible for those builds.