Well I'm having to do that but why spend time on "creativity in programming" when I want the program to do what I want
that's my creative input not ways around problems I shouldn't even have.
It would be perfectly possible to code some assembler behind a goto command Java is only the execution of code behind the instructions, not a sacred cow!
Entry 17.10 in comp.lang.c FAQ list
[11] addresses the issue of GOTO use directly, stating:
"Programming style, like writing style, is somewhat of an art and cannot be codified by inflexible rules, although discussions about style often seem to center exclusively around such rules. In the case of the goto statement, it has long been observed that unfettered use of goto's quickly leads to unmaintainable spaghetti code. However, a simple, unthinking ban on the goto statement does not necessarily lead immediately to beautiful programming: an unstructured programmer is just as capable of constructing a Byzantine tangle without using any goto's (perhaps substituting oddly-nested loops and Boolean control variables, instead)."
Guess what here's how to do it http://en.wikipedia.org/wiki/Java_bytecode_instruction_listings.
Yes two or more goto instructions in Java Bytecode.
goto a7 2: branchbyte1, branchbyte2 [no change] goes to another instruction at
branchoffset (signed short constructed from unsigned bytes
branchbyte1 << 8 + branchbyte2)
goto_w c8 4: branchbyte1, branchbyte2, branchbyte3, branchbyte4 [no change] goes to another instruction at
branchoffset (signed int constructed from unsigned bytes
branchbyte1 << 24 + branchbyte2 << 16 +
branchbyte3 << 8 + branchbyte4)
"The missing "GOTO" that a lot of you are complaining about is missing for a reason."
Yea that reason is nobody's bothered to code it....!