Lack of `GOTO` Support
veloper opened this issue · comments
For true enterprise-level-caliber-code it's clear that the tried-n-true versatility, performance, and maintainability of GOTO is an absolute necessity in order to empower the actualization of language's potential.
GOTO <line>;;;
Param <line> mixed
- String ("One", Forty-Two")
- Int (-1,3,4)
- Float (0.0, 2.4, 1.3e10)
- Object (Line, Number, and possibly Money)
- Array (of <line>s => ["One", 3.5, -5, ..., Line(23)] )
GOTO. Disruptive.
But we need something different from other languages. Something we can have a proper patent. Maybe rethink the term GOTO. What about LEAPTO?
Ideas ideas.
SOARTO?
I like LEAPTO and SOARTO, but how about INNOVATE? You've already got disrupt pretty well covered. You'd have to give up a keyword, but that's disruptive!
WARP <line>
MEETING because it is always a void - it never returns to do any more work. Oh wait, that's LUNCH
+1 MEETING -- that's fantastic!
If the proposed LEAPTO or SOARTO statement is assigning control to the final return statement, I propose JUMPTOCONCLUSION as the instruction name. Seems like additional statements for reassigning control would be sufficiently disruptive. Shall we circle back on this after the catered lunch? Or is post-afternoon coffee better for everyone?
May I humbly suggest that this is all marginal tinkering. What you want instead is COMETO that pulls you in from a labeled line to the COMETO line. That’s disruptive.