4. >= is the "greater than or equal" comparison operator.
Sorry choroba, I just had to...
| [reply] |
honestly, i dont really understand the whole "goto" thing or a legit reason to use it. in my mind though, it is a failure of the programmer to even understand their own logic, which makes them use such a shortcut, especially when there are plenty of other things you can do. | [reply] |
"goto" is older.
Many highlevel constructs are just gotos in disguise and their documentation still contains expressions like "go to beginning of loop"
A language agnostic algorithm description might still say "go to" (like in this case)
And because most use cases have been abstracted away doesn't mean there are no legit applications left for goto
| [reply] |
well, i was just trying to understand it honestly, because in all the CRAZY shit i have had perl do , it has paid off, and i havent ever used "goto". but just because i have never used it, doesnt meant there isnt a reason to use it i reckon. im just a novice anyway, but i do appreciate the user-bility of perl. its like the "engrish" of the computing language :)
| [reply] |
Indeed - processors don't loop, they just jmp - which is extremely similar to the goto that is considered harmful. Fortunately, we have higher level constructs available. (Although even then, I'll often last out of a loop)
| [reply] [d/l] [select] |
Given that the OP was presenting a relatively-plain-English description of an algorithm, rather than actual code (or even pseudocode!), I'm rather confident that "goto 2" was intended to mean "repeat the above process, starting at step 2", not that he used or expected to use an actual goto statement.
| [reply] [d/l] |