Re: QUIT and ABORT

Liste des GroupesRevenir à cl forth 
Sujet : Re: QUIT and ABORT
De : ruvim.pinka (at) *nospam* gmail.com (Ruvim)
Groupes : comp.lang.forth
Date : 24. May 2025, 13:59:08
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <100sfqt$lm0v$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
User-Agent : Mozilla Thunderbird
On 2025-05-24 14:23, mhx wrote:
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.
The standard contains the list of standard words, and the behavior of each standard word is well specified (as far as a standard program concerns). (by design; of course, the standard may contain mistakes)
Therefore, the behavior of a standard system can be falsified using standard program examples. That is, if and only if the system deviates from the specified behavior, this can be demonstrated by some standard program.
See also: <https://en.wikipedia.org/wiki/Falsifiability>

Also, the effect of e.g. a random memory (hardware) error is
not something that can be prohibited.
If you mean that the program cannot read from an allocated memory region due to a hardware error, then this should be an ambiguous condition.
OTOH, access to a random (not allocated) memory region is *explicitly* specified as an ambiguous condition.

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.
Typically, by a test suite you check whether a program conforms to the program's documentation (in the cases that are covered by the test suite).
Conceptually, a program can be falsified by checking that it enters to some ambiguous condition. That is, if a program triggers an ambiguous condition, then the program is not a standard program.
I count implicit ambiguous conditions as well as explicit. For example, somewhere in the standard it says: "A program shall not alter the returned string". Hence, if a program alters this string — it's an implicit ambiguous condition.
So a test suit for programs is a Forth system that stops with a specific message on *any* ambiguous condition.
NB: any test suite for programs proofs nonconformity only in some cases, it cannot proof conformity in all cases.

 Should the first clause be dropped?
I don't think so.
--
Ruvim

Date Sujet#  Auteur
27 Mar 25 * "The Best Programming Language for the End of the World"200Alexis
27 Mar 25 +* Re: "The Best Programming Language for the End of the World"5Martin Nicholas
28 Mar 25 i`* Re: "The Best Programming Language for the End of the World"4Alexis
28 Mar 25 i `* Re: "The Best Programming Language for the End of the World"3Martin Nicholas
30 Mar 25 i  +- Re: "The Best Programming Language for the End of the World"1Alexis
30 Mar 25 i  `- Re: "The Best Programming Language for the End of the World"1Bernd Linsel
28 Mar 25 +* Re: "The Best Programming Language for the End of the World"7anthk
29 Mar 25 i`* Re: "The Best Programming Language for the End of the World"6mhx
29 Mar 25 i +- Re: "The Best Programming Language for the End of the World"1dxf
30 Mar 25 i +* Re: "The Best Programming Language for the End of the World"3anthk
5 Apr 25 i i+- Re: "The Best Programming Language for the End of the World"1anthk
6 Apr 25 i i`- Re: "The Best Programming Language for the End of the World"1sjack
31 Mar 25 i `- Re: "The Best Programming Language for the End of the World"1John Ames
30 Mar 25 +* Re: "The Best Programming Language for the End of the World"88sjack
1 Apr 25 i`* Re: "The Best Programming Language for the End of the World"87dxf
29 Apr 25 i `* Re: Why dial-a-standard is not a thing in Forth86Hans Bezemer
30 Apr 25 i  +* Re: Why dial-a-standard is not a thing in Forth82dxf
30 Apr 25 i  i+* Re: Why dial-a-standard is not a thing in Forth79Hans Bezemer
1 May 25 i  ii`* Re: Why dial-a-standard is not a thing in Forth78dxf
1 May 25 i  ii +* Re: Why dial-a-standard is not a thing in Forth3John Doe
1 May 25 i  ii i+- Re: Why dial-a-standard is not a thing in Forth1Stephen Pelc
1 May 25 i  ii i`- Re: Why dial-a-standard is not a thing in Forth1Anton Ertl
1 May 25 i  ii `* Re: Why dial-a-standard is not a thing in Forth74Hans Bezemer
2 May 25 i  ii  +- Re: Why dial-a-standard is not a thing in Forth1dxf
3 May 25 i  ii  `* Re: Why dial-a-standard is not a thing in Forth72dxf
3 May 25 i  ii   +* QUIT and ABORT (was: Why dial-a-standard is not a thing in Forth)70Anton Ertl
3 May 25 i  ii   i+- Re: QUIT and ABORT1dxf
3 May 25 i  ii   i+* Re: QUIT and ABORT67dxf
3 May 25 i  ii   ii`* Re: QUIT and ABORT66Anton Ertl
4 May 25 i  ii   ii +* Re: QUIT and ABORT64dxf
4 May 25 i  ii   ii i`* Re: QUIT and ABORT63Anton Ertl
5 May 25 i  ii   ii i +- Re: QUIT and ABORT1dxf
5 May 25 i  ii   ii i +* Re: QUIT and ABORT56dxf
5 May 25 i  ii   ii i i`* Re: QUIT and ABORT55Ruvim
5 May 25 i  ii   ii i i +- Re: QUIT and ABORT1Ruvim
6 May 25 i  ii   ii i i +* Re: QUIT and ABORT3dxf
6 May 25 i  ii   ii i i i+- Re: QUIT and ABORT1Anton Ertl
6 May 25 i  ii   ii i i i`- Re: QUIT and ABORT1Ruvim
6 May 25 i  ii   ii i i `* Re: QUIT and ABORT50dxf
6 May 25 i  ii   ii i i  +* Re: QUIT and ABORT3Ruvim
6 May 25 i  ii   ii i i  i+- Re: QUIT and ABORT1Anton Ertl
6 May 25 i  ii   ii i i  i`- Re: QUIT and ABORT1dxf
6 May 25 i  ii   ii i i  `* Re: QUIT and ABORT46Anton Ertl
6 May 25 i  ii   ii i i   `* Re: QUIT and ABORT45dxf
7 May 25 i  ii   ii i i    `* Re: QUIT and ABORT44Ruvim
8 May 25 i  ii   ii i i     +* Re: QUIT and ABORT42dxf
8 May 25 i  ii   ii i i     i`* Re: QUIT and ABORT41Ruvim
9 May 25 i  ii   ii i i     i `* Re: QUIT and ABORT40dxf
9 May 25 i  ii   ii i i     i  `* Re: QUIT and ABORT39Ruvim
9 May 25 i  ii   ii i i     i   `* Re: QUIT and ABORT38dxf
9 May 25 i  ii   ii i i     i    +* Re: QUIT and ABORT2albert
10 May 25 i  ii   ii i i     i    i`- Re: QUIT and ABORT1dxf
9 May 25 i  ii   ii i i     i    `* Re: QUIT and ABORT35Ruvim
10 May 25 i  ii   ii i i     i     +- Re: QUIT and ABORT1dxf
13 May 25 i  ii   ii i i     i     `* Re: QUIT and ABORT33Ruvim
14 May 25 i  ii   ii i i     i      `* Re: QUIT and ABORT32dxf
14 May 25 i  ii   ii i i     i       `* Re: QUIT and ABORT31Ruvim
15 May 25 i  ii   ii i i     i        `* Re: QUIT and ABORT30dxf
16 May 25 i  ii   ii i i     i         `* Re: QUIT and ABORT29Ruvim
16 May 25 i  ii   ii i i     i          `* Re: QUIT and ABORT28dxf
16 May 25 i  ii   ii i i     i           `* Re: QUIT and ABORT27Ruvim
17 May 25 i  ii   ii i i     i            `* Re: QUIT and ABORT26dxf
17 May 25 i  ii   ii i i     i             `* Re: QUIT and ABORT25Ruvim
17 May 25 i  ii   ii i i     i              `* Re: QUIT and ABORT24dxf
17 May 25 i  ii   ii i i     i               `* Re: QUIT and ABORT23Ruvim
18 May 25 i  ii   ii i i     i                `* Re: QUIT and ABORT22dxf
18 May 25 i  ii   ii i i     i                 +* Re: QUIT and ABORT2Anton Ertl
18 May 25 i  ii   ii i i     i                 i`- Re: QUIT and ABORT1dxf
18 May 25 i  ii   ii i i     i                 `* Re: QUIT and ABORT19Ruvim
18 May 25 i  ii   ii i i     i                  `* Re: QUIT and ABORT18dxf
19 May 25 i  ii   ii i i     i                   `* Re: QUIT and ABORT17Ruvim
20 May 25 i  ii   ii i i     i                    `* Re: QUIT and ABORT16dxf
24 May 25 i  ii   ii i i     i                     `* Re: QUIT and ABORT15Ruvim
24 May 25 i  ii   ii i i     i                      +* Re: QUIT and ABORT9mhx
24 May 25 i  ii   ii i i     i                      i+* Re: QUIT and ABORT5Ruvim
24 May 25 i  ii   ii i i     i                      ii`* Re: QUIT and ABORT4mhx
24 May 25 i  ii   ii i i     i                      ii +- Re: QUIT and ABORT1Ruvim
24 May 25 i  ii   ii i i     i                      ii +- Re: QUIT and ABORT1Anton Ertl
24 May 25 i  ii   ii i i     i                      ii `- Re: QUIT and ABORT1albert
24 May 25 i  ii   ii i i     i                      i`* Re: QUIT and ABORT3Anton Ertl
11 Jun 25 i  ii   ii i i     i                      i `* Re: QUIT and ABORT2Gerry Jackson
12 Jun 25 i  ii   ii i i     i                      i  `- Re: QUIT and ABORT1Anton Ertl
24 May 25 i  ii   ii i i     i                      +- Re: QUIT and ABORT1albert
24 May 25 i  ii   ii i i     i                      `* Re: QUIT and ABORT4dxf
24 May 25 i  ii   ii i i     i                       `* Re: QUIT and ABORT3Ruvim
25 May 25 i  ii   ii i i     i                        `* Re: QUIT and ABORT2dxf
26 May 25 i  ii   ii i i     i                         `- Re: QUIT and ABORT1dxf
8 May 25 i  ii   ii i i     `- Re: QUIT and ABORT1Ruvim
5 May 25 i  ii   ii i `* Re: QUIT and ABORT5mhx
6 May 25 i  ii   ii i  +- Re: QUIT and ABORT1dxf
7 May 25 i  ii   ii i  `* Re: QUIT and ABORT3albert
7 May 25 i  ii   ii i   `* Re: QUIT and ABORT2minforth
7 May 25 i  ii   ii i    `- Re: QUIT and ABORT1dxf
4 May 25 i  ii   ii `- Re: QUIT and ABORT1dxf
4 May 25 i  ii   i`- Re: QUIT and ABORT (was: Why dial-a-standard is not a thing in Forth)1albert
5 May 25 i  ii   `- Re: Why dial-a-standard is not a thing in Forth1dxf
30 Apr 25 i  i`* Re: Why dial-a-standard is not a thing in Forth2sjack
1 May 25 i  i `- Re: Why dial-a-standard is not a thing in Forth1dxf
30 Apr 25 i  `* Re: Why dial-a-standard is not a thing in Forth3albert
30 Apr 25 i   `* Re: Why dial-a-standard is not a thing in Forth2Hans Bezemer
30 Apr 25 i    `- Re: Why dial-a-standard is not a thing in Forth1mhx
4 Apr 25 +- Re: "The Best Programming Language for the End of the World"1dxf
5 Apr 25 `* Re: "The Best Programming Language for the End of the World"98dxf

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal