[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gforth] Multiple problems with latest Gforth-CVS

From: Bernd Paysan
Subject: Re: [gforth] Multiple problems with latest Gforth-CVS
Date: Fri, 07 Dec 2012 19:05:19 +0100
User-agent: KMail/4.8.5 (Linux/3.4.11-2.16-desktop; KDE/4.8.5; x86_64; ; )

Am Freitag, 7. Dezember 2012, 18:57:19 schrieb Anton Ertl:
> It has returned for a long time.  If it returns to main(), it used to
> do some cleanup actions and then main() returns (and whatever calls
> main() exits).  Why has that changed?

The gforth-as-library needed some significant refactoring of main(), so that 
people can actually use it. gforth_start(argv, argc) is doing all the setup of 
an engine, including handling the command line paramenters, and returns after 
completion.  This is because a system where Gforth is used to script some 
parts will want it in that state, but will *not* go into interactive mode.  If 
you want to go into interactive mode, you call gforth_quit(), which is 
probably an unintuitive name, but that's, because QUIT has been wrongly named 
by Chuck.

> If (bye) is used in an inner
> invocation of the engine, then it probably should not exit, but that's
> not what David has tried.

Bernd Paysan
"If you want it done right, you have to do it yourself"

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]