4 ms·

Looks like a code block didn't get closed properly, before this phrase: > the functions `recip` and `recip⁺` and not equivalent Several paragraphs after this

Looks like a code block didn't get closed properly, before this phrase: > the functions `recip` and `recip⁺` and not equivalent Several paragraphs after this got swallowed by the code block. Edit: Oh, I didn't realize the article is by the author of the book, Modern C. I've seen it recommended in many places. > The C23 edition of Modern C is now available for free download from https://hal.inria.fr/hal-02383654 https://hal.inria.fr/hal-02383654

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 ago
  I'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 ago
    I 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 ago
      Yeah, 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.
shakabrah 1y ago
It made immediate sense to me it was Jen once I saw the code samples given
zmodem 1y ago
> Looks like a code block didn't get closed properly This seems to have been fixed now.
- perching_aix 1y ago
  I still see it, even after clearing caches, visiting from a separate browser from a separate computer (even a separate network).

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 ago
I'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 ago
  I 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 ago
    Yeah, 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.

shakabrah 1y ago

It made immediate sense to me it was Jen once I saw the code samples given

zmodem 1y ago

> Looks like a code block didn't get closed properly This seems to have been fixed now.

perching_aix 1y ago
I still see it, even after clearing caches, visiting from a separate browser from a separate computer (even a separate network).