SystemTags with non-existing command

	Bottom Previous Topic Next Topic
Register To Post

Capehill

Posted on: 1/4 17:52 #1

Just can't stay away

Is it normal that SystemTags() returns 0 even when command couldn't be found? I was relying it to return -1 rather. Maybe I need to try Lock() before?

joerg

Re: SystemTags with non-existing command

Posted on: 1/4 17:59 #2

Just can't stay away

@Capehill
Are you using SYS_Asynch,TRUE or SYS_Asynch,FALSE?

Capehill

Re: SystemTags with non-existing command

Posted on: Yesterday 9:29 #3

Just can't stay away

@joerg

SYS_Asynch, TRUE.

joerg

Re: SystemTags with non-existing command

Posted on: Yesterday 17:46 #4

Just can't stay away

@Capehill
Quote:

SYS_Asynch, TRUE.

From https://wiki.amigaos.net/amiga/autodocs/dos.doc.txt dos.library/SystemTagList


RESULT

    error -- 0 for success.



        Depending on the mode used, the value returned can mean

        different things.



        SYS_Asynch,TRUE:

                 -1 = indicates System() failure.

                  0 = indicates System() success, 



        SYS_Asynch,FALSE:

                 -1 = indicates System() failure.

                  n = non-zero  program error.

                  0 = indicates program success.

Since SYS_Asynch, TRUE obviously can't wait for the completion of the program/command to be executed, which is only possible with SYS_Asynch, FALSE, it can't return any error/return code of the program/command to be executed, it can only return success/failure if starting the async shell process, which should load that program/command, worked (0) or not (-1, usual reason: out of memory).
Independent of any errors which may happen in that async process, incl. failure of the async shell loading the program/command.

Just a wild guess, but maybe using SYS_Asynch,FALSE with


"run <>NIL: command"

could help and return more usable return/error codes.

Register To Post
	Top Previous Topic Next Topic

Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )