Cries can be heard that Microsoft will eliminate the Win32 API from Windows. It bothered me.
This article reassure PB developers:
http://stackoverflow.com/questions/1157 ... e-versions
What do you think of this case?
Win32 API in future versions of Windows?
Re: Win32 API in future versions of Windows?
Discussed previously here for win 8
http://www.purebasic.fr/english/viewtop ... =7&t=47563
Somewhere else before for .Net
And somewhere else in the future for Windows 9
But we don't have any part in the decision making process, so we will have to take what happen.
No much sense in crying about it.
Anyway just think to all the "legacy code" that would cease to work and make your conclusions.
That's what make the people see value behind Windows, else it would be just an OS like OS/2.
http://www.purebasic.fr/english/viewtop ... =7&t=47563
Somewhere else before for .Net
And somewhere else in the future for Windows 9
But we don't have any part in the decision making process, so we will have to take what happen.
No much sense in crying about it.
Anyway just think to all the "legacy code" that would cease to work and make your conclusions.
That's what make the people see value behind Windows, else it would be just an OS like OS/2.
"Have you tried turning it off and on again ?"
Re: Win32 API in future versions of Windows?
Even if the Win32 API is removed, PB will follow the trend, so PB developpers won't even notice it. You might want to read this: http://www.purebasic.fr/blog/?p=431
Re: Win32 API in future versions of Windows?
Thank you for your responses. Information from Fred is very comforting. I bless the day when I decided to use the Pure Basic, the best system for application development. Fred: I wish you good health and determination to continue the development of PB.
Re: Win32 API in future versions of Windows?
Somehow it's pretty easy if they only allow "managed executables" in their new OSes....
That's what M$ is trying to do, maybe later M$ will ask users to run "signed executables" only eventually, it's fun how M$ make their OS more and more useless.
That's what M$ is trying to do, maybe later M$ will ask users to run "signed executables" only eventually, it's fun how M$ make their OS more and more useless.
This field was left intentionally as signature.
Re: Win32 API in future versions of Windows?
Win32API isnt going away. It's a basic part of the OS and can't be removed without major rewrites.
They could disallow access to it. But why would they do this? It would brake all none .NET applications out there. And .NET itself is based on Win32API, would need some major rewrite too.
They could disallow access to it. But why would they do this? It would brake all none .NET applications out there. And .NET itself is based on Win32API, would need some major rewrite too.
Re: Win32 API in future versions of Windows?
Well, Win 8.1 apps... if they are fully compliant, do they use any WinAPI? Just a wonder...
( PB6.00 LTS Win11 x64 Asrock AB350 Pro4 Ryzen 5 3600 32GB GTX1060 6GB - upgrade incoming...)
( The path to enlightenment and the PureBasic Survival Guide right here... )
( The path to enlightenment and the PureBasic Survival Guide right here... )
Re: Win32 API in future versions of Windows?
An enjoyable read and helps explain what makes PB unique in the world of software development.Fred wrote:... You might want to read this: http://www.purebasic.fr/blog/?p=431
One other great feature of PB I forgot to mention in my comment there is free lifetime PB updates!
Re: Win32 API in future versions of Windows?
Of course. Even if you use WinRT your using the Win32API. Microsoft has added functions to the WinAPI to support WinRT like CreateFile2.blueznl wrote:Well, Win 8.1 apps... if they are fully compliant, do they use any WinAPI? Just a wonder...
Here is a list of Win8 and 8.1 Win32API functions: http://msdn.microsoft.com/en-us/library ... 85%29.aspx