WOW! The tenacity of you guys figuring this out is absolutely amazing!! Should some restriction/guidance be included in the documentation?
Extend the functionality of SysTextScreenSize function
Ditto on CMS, where Rexx was developed. Ignoring BFS and SFS, CMS Rexx will simply search the accessed disks in mode ketter alphabetical order, applying its defined algorithim for naming conventions. This is why the system disks are usually at mode letters S and Y and a 'Tools' disk is earlier in the search order. If you're a Developer, as I was, you simply develop your test version on your 'A' disk and use it. THE uses a similar technique by letting you define a 'Macro Path' that lists the search...
Ken, Please provide the details here, especially the version of THE and the W10 update history at Settings>Update & security>update history, as well as your hardware and interpreter.
See bug #960
It's a mixed blessing(?) that we live with. Note that in your case if a user of another OS using Regina (with the usual ft of .rexx) had sent you some sample code and you had put it in the same folder some years ago, your code would have found it. You might be surprised by the result, but it might be of help!
Alfredo, Isn't this like trying to distribute Windows code to a Linux user? Why would you distribute code to a user who couldn't run it?
Time(E) certainly behaves differently than what is documented. This simple THE macro: call time 'R' say result b=0 do i=1 to 10000 b=i+1 End say time('E') exit yields: 0 0.003000 I'd guess that your simple Say Time('E') is actually 'correct', since the definition reuires a Reset. Also, I checked the Object Rexx Beta draft and the current doc was directly copied from that OS/2 manual which, in turn, reworded it from the VM Ref of the same timeframe. I'm in favor of documenting the actual behavior,...