Perhaps "namespace-qualified symbol" assuming that is defined in the section on Namespaces? Just a thought.
This was an interesting one to figure out! The problem (s) are: using at[3] instead of at(3) and deciding on the meaning of "a stem not having an item associated with a tail". Thanks to trace i, the evaluation starts with s.~at which yields 23 the same as s.~at(). Then 23 gets the message '[3]' - a 'shorthand 'for substr(3,1) - which is the null string. So that leaves the second question. If a stem has a default value then every possible tail has a value. Might be good to explicitly state that in...
I have always disliked the term "classic Rexx" as I believe it is ambiguous. There is the "version" that corresponds to the VM implementation, the TRL2 version, the ANSI standard version and perhaps others. The REXX language has evolved (thank goodness!) since its original implementation and that has necessitated changes which sometimes make programs that ran under an earlier version fail under a newer version. In most cases, small changes to those programs will get them running again. I think that...
I agree that the RXPIPE package is probably NOT 64 bit based on this new information but it IS apparently an OS/2 package! I have no experience in the compatibility of OS/2 packages, especially compiled ones (the files are an exe and 2 dll's), with 32 bit Windows so I cannot say if one should expect them to work in that environment. Perhaps someone else might know the answer to that question.
Before I post my thought on this problem, let me make sure I understand the environment where you experience the failure. You have a PC that is running 64 bit Windows and has ooRexx 5.0.0 installed and running correctly. You now try to run portable 32 bit ooRexx 5.0.0 on that system which is known to be a supported scenario. However, you experience a problem seemingly related to a private package named RXPIPE. My question is what bit-ness is the RXPIPE package that is being run? If you have it installed...
Update document copyright dates to 2025
Problem with SysCls on Windows
Marking this as Pending w/ no work items.