Greetings ooRexx'ers,
To René's point about "not to break people's programs"... I have not tried on
Windows ooRexx in a while... is the .CMD extension still checked as one of the searched
extensions
Customers who were on OS/2 and migrated to Windows could have ended up with
.CMD extensions that way.
I am thankful,
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/
René Jansen via Oorexx-devel wrote:
I would support that. For crexx a change was needed, so what Josep Maria says; I would also fall back to .rexx in the code that locates files as a second choice; this because is it meant as a
suggestion to keep things clean and separate, and not to break people’s programs.
René.
On 15 Jun 2026, at 16:48, Josep Maria Blasco <[email protected]>
wrote:
Both .orx and .oryx look good to me.
We should be careful, though. Rexxref 7.2.1.1. Locating External Rexx Files says
1. If the searched file is requested by a ::REQUIRES directive without a
LIBRARY option, or the Package methods new and loadPackage when only the name
argument is specified, an attempt to locate a
file using the extension .cls is made.
2. If the calling program has a file extension, then the interpreter will
attempt to locate a file using the same extension as the caller.
3. Some applications using Rexx as a scripting language may define additional
extension types. For example, an editor might define a preferred extension that
should be used for editor macros.
This extension would be searched next.
4. The default system extension, which is .REX on Windows, and both .rex and
.REX on Unix-like systems.
5. If the target file has not been located using any of the above extensions,
the file name is tried without an added extension.
I'd insert a new point to search for .ORX and .ORYX (and its lowercase versions
in Linux) between 4 and 5. The breakage surface appears to be minimal.
Josep Maria
Missatge de Rony G. Flatscher <[email protected]
<mailto:[email protected]>> del dia dl., 15 de juny 2026 a les 16:08:
In a discussion a couple of weeks ago in the context of cREXX it was
proposed that each Rexx
language would use a proper file extension, if the contained code can only
be run by that language,
hence ".crexx". In that discussion, it also became clear that a proper
extension for ooRexx programs
should be used if the program could only be executed by ooRexx.
We already have an extension ".orx" that we could use (associated with the
operating system during
installation), hence suggesting to use that extension for any new Rexx
programs that can only be run
by ooRexx.
---
In this context, another idea, suggestion: if not mistaken, one of the
project names at IBM when
developing "Object REXX" was "oryx". There used to be an oryx logo on the
OS/2 developer CDs, if I
recall correctly. (Back then, quite a few programming languages would use
an animal as their logo.)
Nowadays, not being confined to FAT 8.3 file names anymore, how about
supporting an optional
filetype named ".oryx"? Any comments?
---rony
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
