On Exit question

[TerryRitchie]

@NasaCow

on wikipage of _EXIT you find these instructions:

 If a return value is not 0 the program can handle an exit request at a more convenient time if necessary.
 After being read, the _EXIT value is reset to 0 so store the value when a program delays an exit request.
 Note: Once _EXIT has been used once, you must monitor your program by checking it for user _EXIT requests.
 Don't just use _EXIT once to prevent a user from exiting a program early, as that constitutes bad practice.

....
can you find another way to manage the issue about closing by brute force your program?

Well, that's what I am trying to figure out by copying the wiki example. I was just trying to get it to system out still without doing anything else but it also said you need to an initial _EXIT to enable the use.

@NasaCow

on wikipage of _EXIT you find these instructions:
....
can you find another way to manage the issue about closing by brute force your program?

I just include _EXIT in my checks for the user wanting to leave the program:

Foo = _EXIT

DO
   .
   . <code>
   .
LOOP UNTIL _KEYDOWN(27) OR _EXIT ' ESC pressed or window X clicked

This is actually a great idea, will force run all my normal saving routinues. Does _EXIT in this case retain it value so I can system out afterwards or should I set a flag to retain the value of _EXIT? (Pressing the 'X' multiple times to system out may annoy the user...)

I've never really checked for this. I've always made sure to include an _EXIT check in all my loops where I feel a user may want to leave. I would assume _EXIT contains a testable value only when the X close button is depressed on a window. It would be easy enough to do the following to be sure _EXIT is captured:

Foo = _EXIT
Leave = 0

DO
    .
    IF _EXIT THEN Leave = -1
    .
    . <more code>
    .
LOOP UNTIL _KEYDOWN(27) OR Leave

You could:

DIM SHARED Leave AS INTEGER

somewhere at the top of your code. That way, if you enter another sub/function within the <more code> area that sub/function can set Leave appropriately as well and it will retain the value when sub/function exits. You could even have a check at the beginning of the other subs/functions:

IF Leave THEN EXIT SUB ' or EXIT FUNCTION

that would immediately exit a sub/function if Leave was already previously set. No need to continue further if the user is wanting to exit. Just a few thoughts.