Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.forth    |    Forth programmers eat a lot of Bratwurst    |    117,927 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 116,939 of 117,927    |
|    Anthony Howe to Ruvim    |
|    Re: bye with exit status    |
|    06 Nov 24 11:51:16    |
      From: achowe@snert.com              On 2024-11-06 07:12, Ruvim wrote:       > For example, the following code fragments have stack effect ( n -- ⊥ )       > and use n as the process exit status:       >       > SwiftForth "exitstatus ! bye"       > VfxForth "exitcode ! bye"              Don't like this behaviour; it comes off like a side-effect.              > Gforth "(bye)"              I'd be content with `(bye)`.              > ciforth "exit-code ! bye"       > mf3 "sysexit"       > Post4 "bye-code"              Just because there was nothing in the standard and I was not aware of what       others did. I had considered `OSEXIT` or `EXIT-TO-HOST`, but neither of these       come off as related to `BYE` when you see the name.               (bye)        bye-code        bye-status        bye-exit        bye-bye ( ok I'm getting silly; point is it should relate to BYE )              > SP-Forth "halt"              I do _not_ like this choice, because I associate "halt" with system halt, ie.       `shutdown -h now` or `halt(1)`.              And certainly not `hcf`.              > Could you suggest some names for the word with this functionality so that       one of       > them can be standardized?       >       > This word should not output any messages.                     --       Anthony C Howe       achowe@snert.com BarricadeMX & Milters       http://nanozen.snert.com/ http://software.snert.com/              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca