This isn't about a single person as such...
...more about the people who decieded to put semicolons in Java.

My god, the amount of hours I've spent in Eclipse (whch regularly fails to point out missing semicolons unlesss you move the cursor off the line) wondering why I can't get the motherplopping thing to compile exceeds the amount of time I've been alive.





WHY ORACLE SUN WHY?

EDIT: I can't switch to another coding language as I am writing mods for Minecraft, and it's written in Java (with some amusing notes and javadocs actually :D)
(D.I.pshit solved another case on, Fri 5 Oct 2012, 19:05, 6 replies)

Have you tried SciTE?

( brb shitting dahlias, Fri 5 Oct 2012, 19:17, closed)

or geany?

(Misery McUglywife an attention seeking sociopathic fuckstain., Fri 5 Oct 2012, 20:05, closed)

Have you considered crochet?
You're clearly too dim for coding.
( Dr. Shambolic je suis charlie, Fri 5 Oct 2012, 20:23, closed)

Wait
How can you forget the semicolon?!
That's like forgetting to put the left foot after the right foot while walking (after a while anyway, but that goes for walking too)

And Shirley it was Sun not Oracl.
(bovine intervention, Fri 5 Oct 2012, 20:59, closed)

Eclipse started out at IBM
And split from them a long time ago.
(Rilux might be pregnant and has bum-aids, Fri 5 Oct 2012, 21:44, closed)

Have you tried Groovy?
No semicolons needed
( le brian, Fri 5 Oct 2012, 23:15, closed)

Be grateful that it is at least consistent about it
In COBOL, the full stop is used in the same way, but you don't necessarily need to use it in a lot of cases. For example, you can write:

IF condition
   PERFORM thingummy
   PERFORM summat-else
   PERFORM delete-a-load-of-shit
.

MOVE x TO y.

The PERFORMs don't have full stops because they're inside the IF, but the full stop that follows terminates the IF. Now if I shift the MOVE like this

IF condition
   PERFORM thingummy
   PERFORM summat-else
   MOVE x TO y.
   PERFORM delete-a-load-of-shit
.

and forget to remove the full stop at the end of that statement (which is perfectly valid), then this full stop terminates the IF, delete-a-load-of-shit gets called unconditionally, and the final full stop is still valid. No compile errors get generated.

I did this once and managed to trash a production database that took the DBAs two days to recover (thankfully, it wasn't a critical one). Now I only put full stops in if they're mandatory, and use END-IF to terminate an IF statement. Much safer that way!
(An eejit passing by in a purple satin skirt with sparkly bits, Sat 6 Oct 2012, 12:51, closed)