On 20.10.2025 16:08, Gilbert Barmwater via Oorexx-devel wrote:
That's interesting! I knew that there were platform-specific versions but only worked with the
Windows version as I have no ability to build or test the *nix version. In fact, I found a
problem with ArgumentParser.h ! I'm also very interested in knowing if there are functional
differences.
BTW, the code is really C, not C++, and I have made changes to "upgrade" parts of it to use the
equivalent C++ code. I'm happy to supply those changes if you are interested.
Yes, I would be interested!
The current implementation is now the same for Windows and Unix, here the links to "rexx.cpp" after
the commit:
* rexx.exe (Windows):
<https://sourceforge.net/p/oorexx/code-0/HEAD/tree/main/trunk/utilities/rexx/platform/windows/rexx.cpp>
* rexx (Unix, same as Windows):
<https://sourceforge.net/p/oorexx/code-0/HEAD/tree/main/trunk/utilities/rexx/platform/unix/rexx.cpp>
Maybe you could add the new "-o[g]" logic to your C++ version?
---rony
On 10/20/2025 8:08 AM, Rony G. Flatscher wrote:
While going through the rexx launcher code, I stumbled over some Windows-specific differences
compared to the Unix solution, which add some complexity that may not be necessary, like an
additional Windows-only ArgumentParser.h and the use of GetCommandLine() in the Windows version
only.
Here are the referenced files:
utilities\rexx\platform\unix\rexx.cpp
utilities\rexx\platform\windows\rexx.cpp
common\platform\windows\ArgumentParser.h
Would there be anything lost function-wise if I were to change Windows' rexx.cpp to match the
Unix' rexx.cpp and forgo GetCommandLine() and ArgumentParser.h altogether?
---rony
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
