Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.forth > #58366
| From | Alex <alex@rivadpm.com> |
|---|---|
| Newsgroups | comp.lang.forth |
| Subject | Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) |
| Date | 2017-04-29 18:46 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <oe2jbs$6bp$1@dont-email.me> (permalink) |
| References | <332b84e4-3e3d-426c-9a27-42b25b9979a5@googlegroups.com> <o2941d$pth$1@dont-email.me> <2016Dec8.165835@mips.complang.tuwien.ac.at> <o2coqg$o7l$1@dont-email.me> <oe1sa7$50t$1@cherry.spenarnc.xs4all.nl> |
On 4/29/2017 12:09, Albert van der Horst wrote: > In article <o2coqg$o7l$1@dont-email.me>, Alex <alex@rivadpm.com> wrote: >> On 12/8/2016 15:58, Anton Ertl wrote: >>> Alex <alex@rivadpm.com> writes: >> >>> >>>> . Error recovery may not work correctly on the saved EXE. >>> >>> What do you mean with that? >>> >> >> Exception handling may change the environment of the system between an >> initialisation and the point where it's saved; but when the saved EXE is >> run, everything the system manages returns to the initialisation state >> (qv file handles). Under Windows, automated guard page exceptions to >> change reservations to allocations on the stack are one where the >> application programmer has no control. > > The proper exception handling for an application program is > to have all foreseen exceptions caught and consider all unforeseen > exceptions fatal. Fatal exceptions should abort the application, > not fall into the QUIT interpreter loop. 1] Well, of course, since by definition fatal errors are fatal, but not all unforeseen errors can be expected to be fatal and abort; since that would make a development environment very difficult indeed. Re-entering QUIT allows the application to be debugged. > This is what is built in into the -c (compile) option of ciforth). > Assuming the user of an application can do some useful error > recovery within Forth is in general invalid. I respectfully disagree; for example, division by zero. > > This is not to say that special situations may not arise. > The application may be geared towards very knowledgeable users, or > a turnkey control system may be designed to do a warm start > with as little danger as possible. Yes. WF32 does have a mechanism for this; there's a sequence that does initialization which can then call the end user's application. The default application is to have QUIT executed. > >> -- >> Alex > > Groetjes Albert > > 1] This might even be a security leak. I doubt it; one could consider the entire Forth system as a security leak in that case. > -- Alex
Back to comp.lang.forth | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
how to create standalone EXE from inside forth with actual working environment (in forth or c) make.kmatze@gmail.com - 2016-12-07 02:55 -0800
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) Julian Fondren <julian.fondren@gmail.com> - 2016-12-07 03:26 -0800
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) make.kmatze@gmail.com - 2016-12-07 05:31 -0800
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) Julian Fondren <julian.fondren@gmail.com> - 2016-12-07 05:50 -0800
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) Alex <alex@rivadpm.com> - 2016-12-07 13:50 +0000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) stephen@mpeforth.com (Stephen Pelc) - 2016-12-07 20:24 +0000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) Alex <alex@rivadpm.com> - 2016-12-07 22:05 +0000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) stephen@mpeforth.com (Stephen Pelc) - 2016-12-08 09:13 +0000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) "Elizabeth D. Rather" <erather@forth.com> - 2016-12-07 14:59 -1000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) Ron Aaron <rambamist@gmail.com> - 2016-12-08 06:50 +0200
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) JUERGEN <epldfpga@aol.com> - 2017-04-29 04:58 -0700
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) anton@mips.complang.tuwien.ac.at (Anton Ertl) - 2016-12-08 15:58 +0000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) Alex <alex@rivadpm.com> - 2016-12-08 23:04 +0000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-29 13:09 +0200
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) Alex <alex@rivadpm.com> - 2017-04-29 18:46 +0100
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-04-30 12:09 +0200
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) "Elizabeth D. Rather" <erather@forth.com> - 2017-04-30 09:35 -1000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) Alex <alex@rivadpm.com> - 2017-04-30 22:23 +0100
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) "Elizabeth D. Rather" <erather@forth.com> - 2017-04-30 13:50 -1000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) stephen@mpeforth.com - 2017-01-02 03:59 -0800
Re: how to create standalone EXE from inside forth with actual albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2017-01-02 15:10 +0100
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) "Elizabeth D. Rather" <erather@forth.com> - 2017-01-02 07:43 -1000
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) stephen@mpeforth.com - 2017-01-02 04:01 -0800
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) albert@cherry.spenarnc.xs4all.nl (Albert van der Horst) - 2016-12-07 15:58 +0100
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) make.kmatze@gmail.com - 2016-12-08 01:32 -0800
Re: how to create standalone EXE from inside forth with actual working environment (in forth or c) make.kmatze@gmail.com - 2017-01-02 03:39 -0800
csiph-web