Re: bye with exit status

Liste des GroupesRevenir à cl forth 
Sujet : Re: bye with exit status
De : albert (at) *nospam* spenarnc.xs4all.nl
Groupes : comp.lang.forth
Date : 06. Nov 2024, 14:58:15
Autres entêtes
Organisation : KPN B.V.
Message-ID : <nnd$0ae0726e$285fa991@9835fe8fe92a08c6>
References : 1
User-Agent : trn 4.0-test77 (Sep 1, 2010)
In article <vgfmfe$22uop$1@dont-email.me>,
Ruvim  <ruvim.pinka@gmail.com> wrote:
Many Forth systems running under an operating system provide
system-specific capabilities to terminate with an exit status [1].
Note that it is not Forth-system-specific but operating-system specific.
Once you leave the Forth, the exit status is non-existent, as far
as Forth is concerned.

>
For example, the following code fragments have stack effect ( n -- ⊥ )
and use n as the process exit status:
>
  SwiftForth "exitstatus ! bye"
  VfxForth   "exitcode ! bye"
  Gforth     "(bye)"
  ciforth    "exit-code ! bye"
  mf3        "sysexit"
  Post4      "bye-code"
  SP-Forth   "halt"
>
Could you suggest some names for the word with this functionality so
that one of them can be standardized?

A turnkey process should not detect an error, or if it is, that
error should be the users fault.
In ciforth I immediately terminate a turnkey process in case of an error.
(The user has an alternative: starting a Forth, then 'SOMETHING CATCH.
He misses nothing.)
The error number is the same as reported in the interpreter and is
documented in the application, or the Forth itself.

>
This word should not output any messages.
Which word? Do you propose the functionality of Gforth's (bye)
in the standard?

>
>
There are at least three different notions of premature termination of
code execution:
  — return from a Forth definition (to the caller)
  — terminate a thread/task
  — terminate the process
And they should not be confused.

IMO all error conditions should have a distinct error number.
So a distinction between the conditions must be made in the
documentation of this error number. No need to theorize about
a common convention between the types of error.

The second set me thinking. This means that EXIT-CODE should be
a user variable. I follow Chuck Moore, I build that bridge if
I must cross the Rubicon.

[1] <https://en.wikipedia.org/wiki/Exit_status>
--
Ruvim
>
--
Temu exploits Christians: (Disclaimer, only 10 apostles)
Last Supper Acrylic Suncatcher - 15Cm Round Stained Glass- Style Wall
Art For Home, Office And Garden Decor - Perfect For Windows, Bars,
And Gifts For Friends Family And Colleagues.

Date Sujet#  Auteur
6 Nov 24 * bye with exit status19Ruvim
6 Nov 24 +- Re: bye with exit status1albert
6 Nov 24 `* Re: bye with exit status17Anthony Howe
6 Nov 24  `* Re: bye with exit status16minforth
6 Nov 24   `* Re: bye with exit status15mhx
7 Nov 24    +* Re: bye with exit status10Ruvim
7 Nov 24    i`* Re: bye with exit status9Anthony Howe
7 Nov 24    i +* Re: bye with exit status5Ruvim
8 Nov 24    i i+- Re: bye with exit status1mhx
8 Nov 24    i i`* Re: bye with exit status3Anthony Howe
8 Nov 24    i i `* Re: bye with exit status2Ruvim
8 Nov 24    i i  `- Re: bye with exit status1Anthony Howe
8 Nov 24    i +- Re: bye with exit status1Ron AARON
8 Nov 24    i `* Re: bye with exit status2albert
8 Nov 24    i  `- Re: bye with exit status1minforth
8 Nov 24    `* Re: bye with exit status4Anton Ertl
8 Nov 24     `* Re: bye with exit status3Ruvim
8 Nov 24      `* Re: bye with exit status2Anton Ertl
8 Nov 24       `- Re: bye with exit status1Ruvim

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal