Re: QUIT and ABORT

mhx@iae.nl (mhx) writes:

On Sat, 24 May 2025 9:20:57 +0000, Ruvim wrote:
>
[..]

In a standard system, any behavior that is not explicitly allowed by the
standard (and can be detected by a standard program) is prohibited.

>
This can't be falsified - there is no list which enumerates all possible
behavior.

If you throw a standard program at the system and it behaves
differently from what the standard specifies, the system is not a
standard system.  This looks like a falsification of the claim "This
system is a standard system" to me.

There is a test suite (maintained by Gerry Jackson) that tests a
system for standards conformance, but as Dijkstra said, tests can only
prove the presence of bugs, not their absence.

Also, the effect of e.g. a random memory (hardware) error is
not
something that can be prohibited.

It's probably pretty hard to implement a standard system on broken
hardware.  It's probably better to use working hardware instead.

In any case, if the system deviates from what the standard specifies,
it does not matter whether that's because of a bug in the system
software or breakage in the hardware.

In a
standard program, any behavior that is not explicitly prohibited by the
standard is allowed.

>
This can easily be falsified with a extensive test suite.

I fail to see how.  Instead, Jonah E. Thomas once had the project of a
Forth system (written in Forth) that would do its utmost to only
execute standard programs and report deviations; but that would catch
only cases that happen in the particular execution of the program.
Quite a bit later the C and C++ world introduced "sanitizers" which
follow the same principle (and have the same shortcoming).

- anton
--
M. Anton Ertl  http://www.complang.tuwien.ac.at/anton/home.html
comp.lang.forth FAQs: http://www.complang.tuwien.ac.at/forth/faq/toc.html
     New standard: https://forth-standard.org/
EuroForth 2023 proceedings: http://www.euroforth.org/ef23/papers/
EuroForth 2024 proceedings: http://www.euroforth.org/ef24/papers/