When a program quits with an errorcode in a script - the script doesn't stop running like it should even with failat set lower than the returncode. So failat is basically doing nothing in 3.1.4.
Here's an image trying to illustrate the issue, setresult is a simple program a friend wrote that basically just quits with the argument given as returncode.
NinjaCyborg wrote:So you butt in to a conversation with nothing useful to say, give bad advice, and then somehow I'm the rude one when I tell it how it is?
The entire team, was, and still is a very small group of people and the work carried out by us was extremely extensive given the size and manpower available.
We had to face bugs dating back to 1993 (and many times even before the nineties), and mess up with ancient programing languages like BCPL and a lot of compiler specific dependencies which were not documented or evident at first sight. The work we did was truly monumental, and I am not saying this because I want to brag, I am telling you this so that you understand and apreciate all the hard work we did for our hobby, which I am sure is yours too.
That said, I understand and respect that you particularly have lots of different points of view regarding AmigaOS or us as a team, but please be empathic and more kind when addressing them as we are all people trying to push our hobby a little bit forward and sometimes being so harsh or bitter against any of us, certainly only helps to kill our motivation.
Back to topic (sorry for my long rant):
The bug has already been reported internally. It will be addressed in the upcoming update fix to 3.1.4 which will be released in the near future (free of charge for 3.1.4 customers).
We are still collecting and fixing bugs, as despite what you could think, we had a surprisingly low occurence of them, despite our forecasts.
It might probably be addressed as a fix performed by a new version of SetPatch.