2 comments

  • dzaima8 minutes ago
    &gt; gcc, however, always defines FLT_ROUNDS to 1<p>Well, considering that gcc doesn&#x27;t support the FENV_ACCESS pragma, and as such all fesetround calls are always UB, it is valid for it to act as if the rounding mode never changes from the default :)
  • MisterTea1 day ago
    As someone who loves and enjoys writing Plan 9 c, all I can say is &quot;standard c&quot;, whatever that means these days, is a mess. Too many things to name ranging from the only two oss compilers being bloated monsters, post c99 additions being pointless, in-line asm ruining portability*, and POSIX can die in a fire (along with typewriter terminals.)<p>I have a friend who is currently on the C committee and is likely going to leave because of all the bad ideas which have both been implemented and going to be implemented.<p>* No, spamming a million ugly #ifdefs all over the source files is gross and hard to read. Split up the code dammit.
    • glouwbug29 minutes ago
      Plan 9 inheritance is really nice. You can still use it with `gcc -fplan9-extensions`. It builds some nice polymorphic workflow an array of tagged enum void pointers
    • 20198432 minutes ago
      &gt;post c99 additions being pointless<p>Atomics are necessary nowadays though.
      • 38362936481 minute ago
        As a part of the language? Are they really? You can do it all with library functions that just take regular int* (and so on).<p>Not that I&#x27;d want it, I like complex type systems, but I see it as philosophically consistent with C.