Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #26733
| From | "Ed" <invalid@invalid.com> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: ABORT" ABORT QUIT THROW and all that |
| Date | 2013-10-29 16:01 +1100 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <l4nfhr$p8j$1@speranza.aioe.org> (permalink) |
| References | <526e62cf$0$1670$e4fe514c@dreader35.news.xs4all.nl> |
Albert van der Horst wrote:
> ...
> It seems to be a bit of a missnomer. It is *not* an
> ABORT adorned with a message. All ABORT" signify situations
> where I want to give the user a second chance, after he
> has seen the message.
> In other words a ABORT" is bound to be caught, not abort.
> Fortunately the standard defines ABORT" as a THROW with
> a special code.
Left uncaught, ABORT" is required to execute ABORT which
in turn executes QUIT. It is my understanding that if caught,
ABORT" will *not* print the message associated with it.
In my system uncaught errors eventually execute (abort) which
looks something like this:
: (abort) ( -- ) s0 @ sp! fs0 @ fsp ! ... quit ;
Typically a turnkey would modify QUIT so that the app exits
back to the OS, perhaps with an error code.
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
ABORT" ABORT QUIT THROW and all that albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-10-28 13:12 +0000
Re: ABORT" ABORT QUIT THROW and all that "Ed" <invalid@invalid.com> - 2013-10-29 16:01 +1100
Re: ABORT" ABORT QUIT THROW and all that Bernd Paysan <bernd.paysan@gmx.de> - 2013-10-29 16:52 +0100
Re: ABORT" ABORT QUIT THROW and all that "Ed" <invalid@invalid.com> - 2013-10-30 12:01 +1100
Re: ABORT" ABORT QUIT THROW and all that "Ed" <invalid@invalid.com> - 2013-11-02 12:55 +1100
csiph-web