Re: Creating a console app

Actually, no. Your "foo" definition used as STARTER crashes because
it executes the exit (semicolon) -- which returns to nowhere. Any
application defined, including pure windows applications, must be
a loop that executes your code until its termination, at which time
it must exit properly as Mike Ghan has already noted.

So, the following would work (but be almost useless):

: foo
    1000 0 do ." bar" cr 1000 ms loop
    0 ExitProcess ;

STARTER foo
PROGRAM foo.exe

Rick

On Sunday, October 12, 2003, at 04:31 PM, Jeff wrote:

> Hello Rick,
>
> Sunday, October 12, 2003, 5:08:22 PM, you wrote:
>
> RV> make sure that your application does enough PAUSE equivalents to
> RV> keep the system happy.
>
> Hmm. I assume that's why this will crash:
>
> : foo ( -- ) ." bar" cr ;
>
> starter foo
> program foo.exe
>
> RV> You only use 'MAIN if you don't want or need a console. In order
> RV> to have the console created and active, you must use STARTER; just
>
> However, I don't want the end user access to the SwiftForth system.
> I've made a meta-compiler for the ARM that will be non-interactive and
> just take a filename as a command line argument. I could use message
> boxes to display errors, but I'd rather use an console window if I
> could.

----------------------------------------------------------------------
sftalk_at_forth.com The SwiftForth programming discussion email list
To unsubscribe, send subject "unsubscribe" to sftalk-request_at_forth.com
For list command help, send subject "help" to sftalk-request_at_forth.com
Message archives are located at http://www.forth.com/archive/sftalk
----------------------------------------------------------------------
This list is a forum for SwiftForth users. For product support and bug
reports, please send email to support_at_forth.com
----------------------------------------------------------------------
Received on Sun Oct 12 2003 - 19:41:03 PDT