13K views · Jan 18, 2013 · 1:00:54 · 1 HN recommender · 3 mentions · discussed 2015–2022
Chandler Carruth's GoingNative 2012 talk on Clang, covering how the compiler helps defend C++ code from mistakes. It makes the case for Clang's diagnostics and tooling.
Why Hacker News points people here: Cited in discussions of why Clang exists and its case against GCC.
“Chandler from Google makes the good case here for Clang.”HN comment, 2015
“Chandler from Google makes the good case here for Clang.”
Chandler Carruth makes the case for Clang
Agreed, Chandler from Google makes the good case here for Clang. Chandler Carruth - Clang: Defending C++ from Murphy's Million Monkeys GoingNative 2012 - Day 2 - Clang this video
“GCC was deliberately designed to prevent such usage.”
Stallman quote on GCC being designed to prevent proprietary use
> both clang and GCC are viable bases from which you make your internal tooling. License is not the only factor determining usability of a compiler wrt interfacing with external tools. GCC was deliberately designed to prevent such usage. See this video at 2:22 for a direct quote from RMS on this topic.
“the reason why Clang was created is because GCC was specifically made to prevent it from being used with non-free software.”
Quote on why GCC was built to resist non-free software use
Related, the reason why Clang was created is because GCC was specifically made to prevent it from being used with non-free software. You can find that quote around 3:17 of this talk: this video It turned out to be easier in the long run to write a compiler from scratch, than to work with GCC.
