[The Architect 2.0]

Atli, on 16 February 2012 - 08:50 PM, said:

And he expected you to avoid them as well? That's going a bit overboard.

Yes, yes he did. It wasn't a very big deal, it prevented me from using guard-clauses in most cases and there was an instance or two where it produced some code that highly resembled feces

[jon.kiparsky]

The Architect 2.0, on 16 February 2012 - 10:11 PM, said:

you know what sucked? when our instructors told us that 'break' and 'continue' were just keywords/macros for 'goto' I was pretty sad when that happened.

Yeah, idiot teachers who don't know what they're talking about do suck.

What's next - no ifs, or for or while loops? Those are built on gotos as well... Pure idiocy.

This post has been edited by jon.kiparsky: 23 March 2012 - 08:57 AM

[The Architect 2.0]

^haha yep.

he was a computer science/java-schools guy.

[Opacity]

Wow... I'm so glad I haven't worked with anyone who uses goto yet.

I can only pray that it never happens. I can stand it in assembly and other lower level languages though, considering that it's pretty much all you have there, but if I ever have to deal with it in any higher level languages...

[Abacus-64k]

Good that we don't have to use languages like GOTO++.

[extremeblueness]

lol.

The book I'm using to teach myself Java says that gotos are very bad, a continue being the most efficient thing is rare, and breaks are neccesary.