Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #19425
| From | anton@mips.complang.tuwien.ac.at (Anton Ertl) |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: Forced exit from an infinite loop? (Win32Forth / eForth) |
| Date | 2013-02-04 16:11 +0000 |
| Organization | Institut fuer Computersprachen, Technische Universitaet Wien |
| Message-ID | <2013Feb4.171158@mips.complang.tuwien.ac.at> (permalink) |
| References | <08b7f96d-f522-4b7b-87e9-109c92e06597@googlegroups.com> <510fc304$0$618$e4fe514c@dreader34.news.xs4all.nl> |
albert@spenarnc.xs4all.nl (Albert van der Horst) writes:
>>Is there a way to force a Forth that is stuck in an infinite loop to
>>abort and return to taking commands at the console?
>>
>>Haven't been able to find a way for Win32Forth or eForth -- other than,
>>of course, killing the process and starting it again.
>
>This is a quality of implementation issue.
>gForth allows to type ^C and you're back in the interpreter with a backtrace.
While it is a quality-of-implementation issue, there is a standard
throw code for "User Interrupt", which I take as a suggestion that a
full-featured system should turn a user interrupt (SIGINT in a POSIX
system, generated by Ctrl-C at a normally configured terminal) into
this Forth exception and let the Forth system deal with it; and if the
exception is not caught by the application, the Forth system should
print an appropriate message and continue in the Forth command line,
if the application was started from the Forth command line (OTOH, if
the application was started from the OS command line, I find it
inappropriate and annoying to fall back into the Forth command line).
- 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: http://www.forth200x.org/forth200x.html
EuroForth 2013: http://www.euroforth.org/ef13/
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Forced exit from an infinite loop? (Win32Forth / eForth) AKE <assadebrahim2000@gmail.com> - 2013-02-04 04:36 -0800
Re: Forced exit from an infinite loop? (Win32Forth / eForth) albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-02-04 14:17 +0000
Re: Forced exit from an infinite loop? (Win32Forth / eForth) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2013-02-04 16:11 +0000
Re: Forced exit from an infinite loop? (Win32Forth / eForth) Andy Valencia <user@vsta.org> - 2013-02-04 17:06 +0000
Re: Forced exit from an infinite loop? (Win32Forth / eForth) Bernd Paysan <bernd.paysan@gmx.de> - 2013-02-04 19:53 +0100
Re: Forced exit from an infinite loop? (Win32Forth / eForth) Andy Valencia <user@vsta.org> - 2013-02-05 01:00 +0000
Re: Forced exit from an infinite loop? (Win32Forth / eForth) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2013-02-05 15:26 +0000
Re: Forced exit from an infinite loop? (Win32Forth / eForth) Mark Wills <forthfreak@gmail.com> - 2013-02-04 07:32 -0800
Re: Forced exit from an infinite loop? (Win32Forth / eForth) Coos Haak <chforth@hccnet.nl> - 2013-02-04 21:05 +0100
Re: Forced exit from an infinite loop? (Win32Forth / eForth) Alex McDonald <blog@rivadpm.com> - 2013-02-04 12:32 -0800
Re: Forced exit from an infinite loop? (Win32Forth / eForth) "Elizabeth D. Rather" <erather@forth.com> - 2013-02-04 11:24 -1000
Re: Forced exit from an infinite loop? (Win32Forth / eForth) albert@spenarnc.xs4all.nl (Albert van der Horst) - 2013-02-05 18:01 +0000
Re: Forced exit from an infinite loop? (Win32Forth / eForth) "Ed" <invalid@nospam.com> - 2013-02-05 10:44 +1100
Re: Forced exit from an infinite loop? (Win32Forth / eForth) Mark Wills <forthfreak@gmail.com> - 2013-02-04 23:09 -0800
Re: Forced exit from an infinite loop? (Win32Forth / eForth) AKE <assadebrahim2000@gmail.com> - 2013-02-05 05:06 -0800
csiph-web