How to know if Run() fails?

[airsoftsoftwair]

however in Walkero's case the OS DID have some behaviour, complete lost in Hollywood

I don't quite get what you mean. What is the exact OS behaviour you expect in Walkero's case?

[plouf]

however in Walkero's case the OS DID have some behaviour, complete lost in Hollywood

I don't quite get what you mean. What is the exact OS behaviour you expect in Walkero's case?

in a previous reply you said "i will see if can be standarized someway .."

personally i think that error code should be transparent forwarded to hollywod app , exactly waht OS returns
for example
Linux returns errorcode 127, what command fails/notfound
AmigaOS return 10 , if fails/notfound
etc

i.e. imho the hollywood script app, must forward returncode, from where OS store it, AS IS.. and not standarized like 1/2/3 constants

[airsoftsoftwair]

personally i think that error code should be transparent forwarded to hollywod app , exactly waht OS returns
for example
Linux returns errorcode 127, what command fails/notfound
AmigaOS return 10 , if fails/notfound
etc

i.e. imho the hollywood script app, must forward returncode, from where OS store it, AS IS.. and not standarized like 1/2/3 constants

Ok, I've implemented this now. On Windows there is no standard return code in case the command isn't found. I've decided to just throw 127 as a return code on Windows in that case. On AmigaOS you'll get 10, though, so it's not 100% consistent but it's a very platform-specific thing anyway so I think it's ok.

Code: Select all

- New [Windows/Linux/macOS]: Execute() and Run() will now return code 127 in case the specified program
  couldn't be started because it wasn't found; note that this is different to the behaviour on AmigaOS and
  compatibles where you'll get return code 10 in case a program wasn't found; I've decided to keep the
  default OS behaviour in this case because return values of external programs are highly OS-dependent anyway