ynfnehf
Joined 7 years ago
Karma
247
Submissions
59
Member since
Jan 18
Joined 7 years ago
struct { long unsigned a : 31; } t = { 1 };
What is t.a > -1? What about if a is instead a bit-field of width 32? (Assuming the same platform as in the quiz.) The unsigned preserving rules greatly increase the number of situations where unsigned int confronts signed int to yield a questionably signed result, whereas the value preserving rules minimize such confrontations. Thus, the value preserving rules were considered to be safer for the novice, or unwary, programmer. After much discussion, the Committee decided in favor of value preserving rules, despite the fact that the UNIX C compilers had evolved in the direction of unsigned preserving.Just as a counterpoint to all the negativity in here.
(To be honest, I have never had a bad meatball. So the problem might be with me. Edit: actually, I tested plant-based meat(?)balls once. They were not good.)
And for those confused: this is not published in nature, but in an open access journal owned by nature: "Humanities and Social Sciences Communications". This is not a subsection of Nature, and is rather obscure. I find it unclear what kind of peer-review has been done, but it has certainly not been done well.
This is not some kind of scientific proof of the "Swedish strategy" being crime against humanity. Merely a oddly placed opinion piece.
"For example, my compiler interprets "\n" (a sequence of backslash and character "n") in a string literal as "\n" (a newline character in this case). If you think about this, you would find this a little bit weird, because it does not have information as to the actual ASCII character code for "\n". The information about the character code is not present in the source code but passed on from a compiler compiling the compiler. Newline characters of my compiler can be traced back to GCC which compiled mine."