4 ms·
It is a great book. I prefer the second edition, not the latest one though with what I call "bloated C".
by johnisgood 1y ago
It is a great book. I prefer the second edition, not the latest one though with what I call "bloated C".
- laqq3 1y agoI'm wondering if you could elaborate? I'd be curious to hear more about "bloated C" and the differences between the 2nd and 3rd edition.
- lioeters 1y agoI was curious about this too, and found some discussion related to the topic of "bloated C" when the 3rd edition was announced. The C23 edition of Modern C - https://news.ycombinator.com/item?id=41850017 https://news.ycombinator.com/item?id=41850017 Like this comment: > Wow, the use of attributes like [[__unsequenced__]], [[maybe_unused]] and [[noreturn]] throughout the book is really awful. It seems pretty pedantic of the author to litter all the code examples with something that is mostly optional. Or this one: > Personally this just makes C much more complicated for me, and I choose C when I want simplicity. If I want complicated, I would just pick C++ which I typically would never want. Examples of what people consider "bloat" in newer C standards: _BitInt(N), guard, defer, auto, constexpr, nullptr _generic, typeof, restrict, syntax based tls
- johnisgood 1y agoYeah, I have a comment that I cannot find right now, they mention many of these things as well. They are all C++-esque, i.e. bloat, in my opinion. Edit: oh, you actually did quote me, too: https://news.ycombinator.com/item?id=41854897 https://news.ycombinator.com/item?id=41854897 In any case, thank you.