5 ms·
And this is why I tend to use a slightly smaller subset of some of the features that C-family languages support, along with an abundance of brackets. If I reme
by bArray 8y ago
And this is why I tend to use a slightly smaller subset of some of the features that C-family languages support, along with an abundance of brackets.
If I remember rightly, there is the example:
a = {-1, -1}
x = 0
a[++x] = x
print(a[0] + " " + a[1])
Depending on the language (and sometimes even if you have optimizations set for those that compile to binaries), you'll get a different answer.
I always love (read sarcasm) to see awesome code, such as:
z = a & b > c | d
or:
z = a > b ? c < d ? e : f : g ? h : i
And then of course, the statement: "my code doesn't need comments because the code comments itself"...
- lern_too_spel 8y agoDon't do that. The behavior is explicitly undefined in C. http://c-faq.com/expr/seqpoints.html http://c-faq.com/expr/seqpoints.html
- oblio 8y agoDon't do what, precisely? He listed several examples. And I think he's agreeing with you, he's just sarcastic.
- lern_too_spel 8y agoHe said, "this is why I tend to use a slightly smaller subset of some of the features that C-family languages support, along with an abundance of brackets." C does not support his first example. The standard states that the behavior is undefined.
- bArray 8y ago> If I remember rightly [..] You're probably not wrong, but I specifically remember there was something you could do in order to trick the compiler to allow modification on the left hand side to happen. It could possibly be by having two variable names referencing the same variable - for example. Besides, the whole point was that it's usually not clever "trying to be clever". It just creates confusion. I don't personally believe the majority of people need to test the entire C spec to it's absolute boundary. A subset serves most people perfectly well.
- quickthrower2 8y agoI've recently started working on a code base with great comments and they are worth their weight in gold. Especially class and method level description comments. And doubly especially the class level ones. Also there is none of the code golf in there that you have just given as an example.
- zbentley 8y ago> z = a > b ? c < d ? e : f : g ? h : i That's stylistically ugly but not hard to predict; at some point I had it beaten into my head that ternaries are always at the bottom of the single-character operator precedence stack (I really hope all languages stick to that). I'd expect most people to know this. > z = a & b > c | d That is harder to predict. I wouldn't expect most people to know this one without looking up a precedence list.
- pjmlp 8y agoIt gets better when you compile that C code as C++, as ?: has a different precedence level.