Jason Ninneman and I have moved it to what is almost, but not quite,
idiomatic modern C. We refactored the right way, checking correctness
-against a comprehensive test suite that we built first and verified with
-coverage tools. This is what you are running when you do "make check".
+against a comprehensive test suite that we built first and verified
+with coverage tools (we have 88% coverage, with the remaining 12%
+confined to exception cases that are difficult to reach). This is
+what you are running when you do "make check".
This move entailed some structural changes. The most important was
the refactoring of over 350 gotos into if/loop/break structures. We
We don't need whatever minor performance gains this might collect,
and the choice to refrain will make forward translation into future
languages easier.
-
* There are a few gotos left that resist restructuring; all of these
are in the principal command interpreter function implementing its
state machine.