analog of execve() to resart ourself

@All
Have little issue: have a game which when change settings do a restart of ourself and do it like this:



So, on Win32 and on Linux that "execve()" called, the old process dies/closes, and new ones replace it automatically.

But as on amigaos4, we don't have the same functionality, I need somehow mimic the same.

Currently i have code to run it again:




But then, I need to add proper "quit", but if I add proper quit (like sdl_exit() ), then I quit from the game, and the code for restarting didn't called of course.

Maybe there some analog of execve() we have without needs to worry about all this? Or the only solution there is to make a loop in the main() { }, where do check on restarting the flag and then clean resources and start them again?


In other words, do we have the functionality to restart the whole binary, just by executing it again, without additional code?

Thanks!

Hi, dirty way:
-Create a script like:
Wait 2 SECS
<executable>

And on restart() just before exit/quit "run script" (with SystemTags() or alike)

or add to ReadMe a warning/note to user to (re)run program when saving/changing settings

@jabirulo
Yeah, that both very dirty and not user-friendly ways which I wish to avoid and implement thing properly :).

Or another dirty way:
restart() quits/exit with a "special" RC (example: 99) and launch script is like this:

LABEL restart
<executable>
IF $RC EQ 99 THEN
Wait 2 SECS
SKIP restart BACK
ENDIF

and make script "main program" with icon, instead of <executable>

@javier
That all no go, as I say I need that from C code itself, without additional scripts, pure C code inside of the same game's code.

@kas1e

you can exit from any place in your program using exit(0);
but you most cleanup before calling exit(0);

You should not clean up:

input_file = IDOS->Open("NIL:", MODE_OLDFILE);
output_file = IDOS->Open("NIL:", MODE_OLDFILE);

this are cleaned up by the ASYNC Process.

Quote:

in most of my programs, have a

bool init();

and

void shutdown();

it makes it easier to clean up, and the code looks nicer too. if you do it like that.

Honestly that's bad program design even in a linux environment, but given that....

Quote:

Why not? Surely you already ran the new copy before exiting? You would need to run the new copy asynchronously ofcourse. (which it looks like you do) Unless there is some code that stops more than one copy from running at a time?

Depending on the program design you *might* be able to just reinitialise the program without restarting. There was case in blender where it forked of a new copy to handle the video player, when actually theer was no need, the existing copy just waited for the new one to complete and so I just called the video player code directly in the same context.

Quote:

If that is viable it would be more elegant, then you can send them a patch to fix their lazy code (Maybe not say that though

@broadblues

Quote:

Its problem to clean up when you have many exists, and don’t know what is causing the exit, memory leeks are more likely to happen.