On Thu, Dec 6, 2018 at 1:47 PM Erich Steinböck <[email protected]> wrote:
> I have access to the fully version information, which is 4 digits rather >> than the existing 2. I'd like to expand the return value with this >> information. >> > Yes, that's fine. > > I want to have it just say "Windows" now rather than "WindowsNT" >> > With all this strict focus on absolute compatibility .. this is bold, > isn't it? There's a registry.rex in our trunk that relies on SysWinVer > returning WindowsNT > Would you still keep parse source returning WindowsNT? > That would be a much more disruptive change since that’s the one that people use to distinguish platforms. I suspect the registry.rex example is probably out of date since we only run on NT based versions any more. > > On Thu, Dec 6, 2018 at 7:03 PM Rick McGuire <[email protected]> wrote: > >> I found an example finally of retrieving the version from one of the >> system dlls (thank you stack overflow). I have access to the fully version >> information, which is 4 digits rather than the existing 2. I'd like to >> expand the return value with this information. >> >> Rick >> >> On Thu, Dec 6, 2018 at 11:09 AM Rick McGuire <[email protected]> >> wrote: >> >>> Yeah, I was afraid of that. They deprecate GetVersionEx(), then don't >>> provide a replacement gives the same information and their recommended >>> replacement needs to be updated every new release. I'm thinking we're just >>> going to need to live with that warning message in that particular case. >>> I'm a little worried that they will no longer update GetVersionEx()...in >>> fact, I suspect they already have stopped, since it is still returning >>> 10.00 for Windows 10. The docs I found did recommend using some APIs to >>> query the version of a Windows system dll, but I couldn't find any examples >>> showing how to use them. >>> >>> I was able to eliminate the other three occurrences. Do you agree I >>> should restore that bit? Although I want to have it just say "Windows" now >>> rather than "WindowsNT" >>> >>> Rick >>> >>> On Thu, Dec 6, 2018 at 11:01 AM Erich Steinböck < >>> [email protected]> wrote: >>> >>>> [r11568] changed Rexxutil to use IsWindows10OrGreater(), which doesn't >>>> seem to be defined in Visual Studio 2015 (all other used IsWindowsXXX() >>>> functions are defined). It gives error "Undefined identifier" for me. >>>> >>>> This seems to push the minimum VS requirement to 2017. >>>> Do we want that? >>>> >>>> Also I believe 5.0 can still run on XP, which the new SysWinVer code >>>> doesn't cover. >>>> _______________________________________________ >>>> 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 >> > _______________________________________________ > 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
