To go or not to go (or rather goto)

[Jacob S. Andersen]

There has been a lot of discussion about whether using goto statements is a
good thing or not.

I'm a goto hater! - But on the other hand, can a goto-like structure
sometimes be a great help when writing programs.

The "solution" I will suggest doesn't really fit into Ada as I see it, but
anyway...

Including graphs describing the execution of the procedure (don't know an
English name for it) as a part of the source code to a procedure can make
it possible to exclude goto statements from the textual source, where they
can be hard to trace, while still keeping the freedom of jumping in the
code in the graphical part of the source, where it will be (imho) easier
to trace the jumps.

I don't know of any working programming languages, that works this way,
but I would like to see some.

I suspect that those fancy programming tools with difficult acronyms do
contain something with a similar feature (disallowing goto's, except when
generated by the tool or something like that).

Comments? Why should this be, or not be, in tools and not in the language?

Regards,
Jacob Sparre Andersen.
--
Have you played with your LEGO today?
--
URL's: "mailto:spa...@nbi.dk", "http://meyer.fys.ku.dk/~sparre",
"mailto:spa...@pitt.edu" & "http://www.pitt.edu/~sparre".
--
I move to Denmark today!
--
"We need a plan to diverge from", Fesser