This might benefit from a little more discussion since the ANSI Standard is of no help here.
The purpose of the first token returned from PARSE SOURCE is to provide enough information to the running application that it has a fighting chance of knowing if what it's getting ready to do, will work. If all the current Windows builds do indeed return "WindowsNT" we've had a problem for some time. (I'm still running WinXP; how would I know?) At the very least it should indicate the architecture, if not the OS name, so that the application could be warned about such changes as the enhanced application security and other "improvements". We have had issues with ooRexx backwards compatibility (ain't going there) so I'd say let the string start with "Windows" and suffix it with the appropriate major release indicator string (and architecture). I notice that my version of Regina displays: parse version v ; say v REXX-Regina_3.7(MT) 5.00 14 Oct 2012 --- parse source s ; say s WIN32 COMMAND C:\Chip\bin\rxtry.rx I'd like to see "Windows7(32)". Just about anything is more useful than "WindowsNT". -Chip- On 8/16/2016 2:44 PM, Erich Steinböck wrote: > With René's ooRexx5 buiild on MacOS X we have a new operating system > name "DARWIN", which parse source will return. > > From some older Rexx scripts I can see that we seem to have had builds > which returned "MACOS" as the first parse source token. > > Do we want "DARWIN" to be the OS indicator for our new Mac OS build, > or do we want to use the previous "MACOS" name (backwards compatibility)? > > > Currently all Windows builds return "WindowsNT", all Linux flavours > (Red-hat-based, Debian-based, etc.) return "LINUX". Non-Linux Unixes, > like AIX, HP-UX, or Mac OS, seem to have used to return their own OS > names. > > > I'm also noting that our code base in some areas ignores anything > except Linux or Windows. E. g. some regression are either Linux or > Windows-specific. Or e. g. DARWIN has neither a SysWinVer nor a > SysLinVer function .. > > Your comments are welcome .. > > Erich > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
