Re: [Netrexx-develop] address with stream

[Rony G. F. <Ron...@wu...>]

On 05.03.2022 17:48, René Jansen wrote:
> No, I thinks that is definitely suboptimal. Why don’t we throw a netrexx.lang.AddressEnvironmentException, that the user can catch if they want to?

Also cf. ooRexx 5.0' reference documentation in "rexxref.pdf", chapters "2.1 ADDRESS" and "11.
Conditions and Condition Traps", for the conditions "error" and "failure" w.r.t. problems while
executing a command. If seen helpful one could distinguish both conditions in a field of
AddressEnvironmentException.

---rony

>
>> On 5 Mar 2022, at 16:24, Marc Remes <re...@gm...> wrote:
>>
>>
>> The latest commit exits the NetRexx program when an exception is thrown during ADDRESS invocation.
>> Such exception can occur when the specified environment is not executable, or when a specified stream is unusable.
>> The exitcode is 9.
>> Note, "address bash 'nonexistingcommand'" will not exit, instead processing will complete and say 'command not found'.
>>
>> Personally I don't find such hard exit optimal.
>> Another option is not to exit, and reset the special variable RC to undefined 'RC', where the calling user can find such exceptional condition.
>> Both options could be coded and controlled by a new ADDRESSEXIT option.
>>
>> Your views?
>>
>> This code now also always correctly handles stderr.
>>
>> Marc