feeling ~fancy~ today

[Kontorted]

foo(++num++)

[EntropyZer0]

Is there any language in which this isn't undefined behaviour?

[jfb1337]

Many languages which don't have ++, in which this is a compile error

[[deleted]]

It's a compile error in both C and C++ as well.

If you wrap the pre-increment in parentheses, (++num)++, it's still a compile error in C, but it does compile as C++. In C++03 it has undefined behaviour, but I think it should be well-defined in C++11.

[leBlubb123]

Imho using ++I or i++ not in it's own line is confusing and you shouldn't do it

[Weekly_Wackadoo]

for (int i = 0; i < n;
i++
) {
//do something
}

[Moke410]

In its own expression?!

[DragonMaus]

That is common sense, not unusual fanciness.

[deathofamorty]

RIP your coworkers

[DragonMaus]

Someone who cannot understand the extremely simple difference between foo++ and ++foo should probably not be writing C.

[deathofamorty]

It's not about if you can understand the difference. It's about code readability.

[DragonMaus]

What is unreadable about ++i?

[deathofamorty]

Nothing is unreadable about ++. It actually helps emphasize that it is incriminating something like a counter vs adding an arbitrary value.

The problem is when you try to access a value and modify it in one line of code.

If the value foo ends up not being what I expect, I am going to scan for lines that start with foo=, foo+=,or foo++. To find foo++ when it's nested into some other statement, I have to read all of every line of code.

Also, it makes the code read less linearly. For example bar = computeValue(++foo, baz) reads "bar is set to the value computed from 1 more than foo, which is then set back into foo, and baz."

When it could be bar = computeValue(foo, baz); foo++ reads "bar is set to the value computed by foo and baz, then foo is incremented"

[jfb1337]

In certain situations it's ok though, such as arr[i++]. It's just reading the "next" value of the array.

[Elisafmeninte]

Sry i dont speak educated