Thread: Fixing the Indentation draft

Originally Posted by citizen

>> Oh and n++ is not the same as ++n

We know. But the behavior difference is basically the only reason to prefer one or the other, especially considering looping. Nevertheless, people will look at n++ in a for loop and be like "damn you're not optimizing and writing code at the same time! Shock and horror!"

Just for the sake of keeping a flamewar going, it can be a good habit to use ++n within loops, not for performance reasons, but because of iterators. Although all of the standard iterators will be fine with n++, some custom written iterators do not implement the copy constructor, and thus ++n will work, while n++ will not compile. Thus, ++n everywhere enforces consistency.

I find the point moot. Since ++n and n++ does different things, there are times when you will avoid from using the same syntax. It's also a matter of opinion, because a few construction/destruction/copying of objects isn't going to hurt performance very much unless done very much.
So I usually say go with whatever you fancy and don't worry about it.
And btw, things lacking a copy constructors such as iterators are broken (things which should allow to be copied).

Now, back to the indentation or coding style draft.

Although all of the standard iterators will be fine with n++, some custom written iterators do not implement the copy constructor, and thus ++n will work, while n++ will not compile.

I think those custom iterators need to be fixed.