883

submitted 2 months ago by sjmarf@sh.itjust.works to c/programmer_humor@programming.dev

52 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] ValiantDust@feddit.de 83 points 2 months ago

But are you gonna return something for this method??? You said you'd return an integer, yet there is no return statement!

[-] gregorum@lemm.ee 41 points 2 months ago* (last edited 2 months ago)

and it had better be an integer! it had better be an integer, motherfucker!!

[-] porous_grey_matter@lemmy.ml 17 points 2 months ago* (last edited 2 months ago)

Well yea... If you write "return " that is actually wrong, as opposed to just not having gotten around to filling it in yet

[-] gregorum@lemm.ee 11 points 2 months ago

[-] sik0fewl@lemmy.ca 16 points 2 months ago

This is why I always write my methods from bottom to top. This way I've always got a return statement and I use my variables before they are even declared.

[-] NightAuthor@lemmy.world 4 points 2 months ago

For a second there I thought you might be serious

[-] ShouldIHaveFun@sh.itjust.works 2 points 2 months ago

I do actually use variables before I declare them most of the time. IDEs make it so easy to then generate the declaration with the correct type.

[-] NightAuthor@lemmy.world 1 points 2 months ago

That’s true, in fact I’ve started doing that myself. Same with methods, instead of going and writing the method and then coming back to use it, I’ll write the invocation first.