Hi Michael, The way I read the article you referenced it seems like the Win32 APIs will go away. However, they (will) have replacements that talk to the CLR/.Net runtime. So that means rewriting the Windows-specific parts of ooRexx to use the replacements instead of the Win32 APIs. But the article says that multiple languages, including C++, can be used to code access to those new APIs. While not a trivial task by any means, at least it doesn't mean rewriting all of ooRexx in C#!
Hope that helps (and that I interpreted the article correctly :-)). Gil B. On 5/10/2017 10:36 AM, Michael Lueck wrote: > Greetings team, > > Last time I did not include the article reference in my OP. This time, doing > so: > > "Why Windows must die. For the third time - Microsoft knows Windows is > obsolete. Here's a sneak peek at its replacement." > http://www.zdnet.com/article/why-windows-must-die-for-the-third-time/ > > > In order to be able to run on the new Windows, does that mean coding ooRexx > in C# to run it on top of the .NET runtime? > > I am thankful, > -- Gil Barmwater ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
