On 10.03.2025 18:14, ooRexx wrote:
I mistakenly took ownership of this bug report but then have not managed to solve it, it involves
changes to CMakeLists.txt beyond my knowledge.
Does anyone want to have a go at it or should I mark it as “Won’t Fix” ? The title explains what
it is about.
Looked up what hashbang gets created for Windows and it is "#!/usr/bin/env rexx". On Windows the
first line gets wiped out if it starts with the hashbang "#!".
The hashbang is important on Unix systems as it uses the "/usr/bin/env" program to locate the
executable "rexx" which gets started by the shell supplying the filename that contains the hashbang
as its first argument and is marked to be executable. Hence a command like
./qtime.rex
will cause the shell to locate the binary "rexx" to run it, if qtime.rex is set to be executable on
Unix. (On Windows "qtime.rex" will cause to Windows to execute "rexx.exe" with "qtime.rex" as
argument due to the file extension ".rex". Cf. environment variable PATHEXT and the commands "ftype"
and "assoc".)
Mostlikely that convention will not really change on Unix systems (changing this convention on Unix
would affect literally billions of files).
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.
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
