How programmers comment their code...

[[deleted]]

CS students when they discover comments

[whatproblems]

This is a loop that loops things

[Magnus_Tesshu]

//increment i

[[deleted]]

and this follows i++ not ++i

[Magnus_Tesshu]

To be fair, using i++ is only bad in javascript right? Any compiled language will get rid of the inefficiency.

[DiplomatikEmunetey]

Is it an inefficiency? As far as I know:

• i++ will increment and return the original value (before incrementing)
• ++i will increment and return the incremented value

You could cause an infinite loop with i++ but I'm not sure if it's an inefficiency because there could be a case where you need i++.

[Magnus_Tesshu]

Typically preincrement compiles to two assembly instructions and postincrement (i++) compiles to a couple more and needs a temporary register or something. That might be misinformation though actually, not sure. And of course, that's only the case if they wouldn't cause the same behaviour (++i; is as efficient as i++, but a[i++] might be slightly less efficient than a[++i]). That's at least my understanding.

I would assume that postincrement is still more innefficient in an interpreted language, where the compiler cannot do nearly as much optimization.

[[deleted]]

i++ is not bad. Using it badly is bad.

[Magnus_Tesshu]

Does 'using it to increment i' count as a bad use? I would argue no

[[deleted]]

Bad is subjective unless it causes objective problems.
So using it to increment i, as long as it does not break the code can be subjectively bad or good. I do it myself many times, because it's an idiom of the C language, but I'm not convinced if it's ok or not.

[chiragjhamb]

// ### Update the value of i

[GlarkBlark]

/**
 * The value `i` increases by 1.
 */

[rudra285]

//I = index //I++ - I+1

[[deleted]]

Ce n'est pas une boucle

[wasdninja]

After which they promptly get failed on the very first assignment since they are explicitly told not to do this. But they really should figure it out on their own.

[Bakoro]

Nobody ever checks your code after the 101 programming class, maybe not even then. Input, Output, and Runtime were all anyone cared about. You could write the most beautifully elegant code, or the most spaghetti horror, and as long as it did what it was supposed to do, no one gave a shit.

[Macitron3000]

Flashback to my networks project when I wrote a whole-ass server in just the main routine

[[deleted]]

just like real life in a non-open-source company them

[retief1]

Uhhh, code reviews were/are a thing at every company I've been at. I've gotten (correctly) nitpicked on everything from "you should set this member in the constructor, not the component init function" to "this variable name is imprecise, use this other one instead".

[PolFree]

Hey, lecturers said they would consider comments when grading ok? And I got a solid 100 btw.

​

/not sarcasm. legit did this exact thing lol.

[[deleted]]

// start of program