What's the diference in the real world between i++ and ++i

If you assign it to something, it's between doing the increment before or after the assignment.

>>61186190
>i = 0;
>thisValue = i++;

>i = 0;
>thisValue = ++i;

>>61186214
I know the definition of both.

what does this mean in real working code?

>>61186223
both give the same result, right?

>>61186225
What the fuck are you trying to ask? Elaborate.

>>61186239
give me some real working example.

>>61186190
>>61186214
>>61186223
>>61186225
>>61186231
>>61186239
fuck off, underage kids.
>>>/reddit/

>>61186254
It is mostly personal preference or coding style of your comapny, you mongoloid nigger. Compilers should optimize that shit anyways. It CAN improve performance in some rare cases, but they are neglectable

>>61186258
>>61186272
so basically is the same fucking shit.

Usually only relevant in loops.

x = 0;
array[x++];

x = 0;
array[++x];

The first is array[0] and the second is array[1], so you could have the same starting variable (x) but have some condition that, for example, ignores the first value of an array. Why would you do it like that? I don't know but you could.

Consider this example check to find the end of a null-terminated buffer in a while loop:

if (*current_position++ == '\0') {
  return current_position;
}

If this were used, current_position would be incremented *after* being dereferenced and checked. When we reach the end of the buffer, we set current_position to point to the byte *after* the end of the buffer, which is dangerous if that address is used, since it could result in a segfault. The correct way to do this:

if (*++current_position == '\0') {
  return current_position;
}

This way, current_position is incremented *first*, so when the end of the buffer is found, we return the correct address.
>>61186287
Don't listen to those retards.

>>61186306
>>61186300
that makes sense I guess.
thanks.

>>61186339
Another example.

value = 5;
previous = value++;
// previous is equal to 5

value = 5;
previous = ++value;
// previous is equal to 6

>>61186382
why does the assigment is given before the increment?

>>61186190
Depends on compilers.

int i = 10;
writeln(++i); should print 11 --it performs the unary function (++) before i is used
writeln(i++) sould print 10. But if you call i again, it'll be 11. The unary function is performed afterwards.