I am reading a book called "Teach Yourself C in 21 Days" (I have already learned Java and C# so I am moving at a much faster pace). I was reading the chapter on pointers and the -> (arrow) opera... More on stackoverflow.com

To add to the other answers here, the reason C does not need a dedicated elif operator is because there is not a required delimiter for conditional branches. That is, in C the next statement, whatever that is, follows the keyword (for completeness, a block scope counts as a statement in this case). Because of this, you don't need "fi" or "endif", which would be required in, say, bash if cond; then code else if cond2; then code2 fi fi You can see it becomes more verbose, so elif is there to allow a cascade without the nesting if cond; then code elif cond2; then code2 fi But because C branches are delimited by the end of the next statement, the following are essentially equivalent if ( cond ) { // code } else { if ( cond2 ) { // code2 } } if ( cond ) { // code } else if ( cond2 ) { // code2 } Interestingly, the C preprocessor does explicitly delimit branches with #endif, so it also has an #elif construct (and soon, I hear, an #elifdef and #elifndef so the defined() expression will be unnecessary). More on reddit.com

N = 5 = (101)2 Actually, with 32-bit ints: N = 5 = 00000000000000000000000000000101 So ~N = ~5 = 11111111111111111111111111111010 And when those bits are in a signed int, you have the value -6 More on reddit.com

PRECEDENCE is not the same as order of operation. All precedence says is how the expression is parsed (that ++ applies to b rather than to the binary operand expression that precedes it. The changing of the variable in ++ is called a side-effect. This means that it is some observable change other than the value of the expression. Side effects are only guaranteed to have occurred when you hit a sequence point. There's a seqeunce point at the end of the full expression, but there's also one in your case at each of the left hand side evaluation of the && or || oerators. The problem you're having however isn't any of this. The && and || operators are short-circuiting operators. If the left side of && is false, it never evaluates the right side (including the side effects). Similarly if the left side of || is true, it doesn't execute the right side. More on reddit.com