On 12.03.2025 12:44, Michael Lueck wrote:
Greetings Rony,
Rony G. Flatscher wrote:
As such I would assume to be safe to add the hashbang "#!/usr/bin/env rexx" as the first line
directly to all those files that you found not to have it. Then all Rexx scripts would adhere to the
hashbang pattern.
Is calling env the multi-ooRexx instance safe method?
I have always set my value based on the result of:
$ which rexx
/usr/local/bin/rexx
Also a last step (beyond adding the hashbang) is on Linux file systems, setting the Rexx scrip
file to be executable.
What you do is hardcoding the path to your installation of rexx. If rexx gets installed to a
different directory or if you use the portable version of ooRexx then rexx found via the
environment variable PATH does not get found and does not get used.
The hash bang convention and using env is not a Rexx convention but a general Unix convention, hence
it makes sense to adhere to it.
---
Have you already tested your program with 4.2, 5.0.0 and 5.1.0beta?
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
