Hacker News Reader

There is a still a noticeable difference in performance of a `goto`-based FSM implementation and a switch-in-a-loop one.

And there is a huge performance difference between a computed `goto` implementation of a VM vs. a switch-based one.

Break is not a substitute for any of this use cases.

View on HN

In my current project I use both. Direct coded lexer and a vm using gnu-c &&label.

Couldn't one just macro an implementation of such things that use goto underneath?

Of course. But only if goto was not removed from the underlying language.

I wonder if anyone has done a safe form of goto that does static analysis or something to see if the jump is safe. My only experience was making error handling easier to understand.

It is rather trivial to check if a control flow is reducible (can be a platform requirement, e.g., OpenCL spec demands this). But it is unlikely that you can do too much of a static analysis with a computed goto, and the latter is the most interesting and the most useful form.

Reply on news.ycombinator.com