Mark Gaubatz

For XRANGE operations, add the ability to specify "NON" as a prefix to the descriptive names

Should be consistent throughout the document as either "*nix" or as "Unix-like".

ooRexx Reference Table 8.1 wrong OS reference

For XRANGE operations, add the ability to specify "NON" as a prefix to the descriptive names

ooRexx Reference incorrectly references rexxutil.dll

I concur, but I'm still personally aware of several who are still using and building to VS 2008 and 2010 with their anchoring of major open source projects - despite the availability of later versions - and require VS 2008/2010 build elements be brought into their documented 2017/2019/2022 build processes. This means that the API includes for VS must keep their conditional handling for the present, but perhaps with an advisory of future deprecation? From: Rick McGuire bigrixx@users.sourceforge.net...

I will also note that limits.h is now available for Windows compilations as well.

MSVC has come a long ways since the bypass was put in with #453, supporting VS 2008 and prior; C11 and C17 levels are now supported (minus atomics) with support starting mid-stream in VS 2019. Clang is also "fully" supported as a compiler via clang-cl. Consequently, when __has_include is defined, then the proper level of inttypes.h is included, rather than the 32-bit version attempting to define types for 64-bit, and the proper stdint.h is known to be in play. From: Gil Barmwater orange-e@users.sourceforge.net...