Hacker News new | ask | show | jobs
by GeekyBear 3124 days ago
There were a couple of purely technical reasons for Apple to pursue Clang.

1.) GCC was designed for command line use, not to provide integration (for instance, debugging info) into a modern IDE.

2.) Objective-C was not a priority for those who maintained GCC, but was for Apple.

https://en.wikipedia.org/wiki/Clang
1 comments
fulafel 3124 days ago
The Objective-C story is a little more complicated. Originally Apple had a hostile fork of GCC and even initially refused to provide source code until the FSF lawyers got involved. It's a small wonder the GCC Objective-C support is as good as it is considering the politics.

Debugging info works similarly in all compilers (GCC, MSVC etc) - it's saved in the compiler output and read by the tools like IDEs.

link
GeekyBear 3124 days ago
>For instance, GCC uses a step called fold that is key to the overall compile process, which has the side effect of translating the code tree into a form that looks unlike the original source code. If an error is found during or after the fold step, it can be difficult to translate that back into one location in the original source.

https://en.wikipedia.org/wiki/Clang#Design

link