Unless they rewritten wine in c++ its going to have problems emulating c++ features like objects really really bad. I am not bashing C, but rather pointing out that rewriting the language to mimick an operating system heavily built on C++ is a mistake.
Huh? The Windows API is written almost entirely in C (it dates back to the mid 80's). New Windows features are still exposed through C (though I think some of the Vista features are only going to be exposed through.NET). Things like MFC and.NET Forms are built on top of the Windows API. The only "core" Windows API that I know of uses C++ is GDI+ which was written as a newer and better version of the GDI (which may or may not be built on top of GDI and some undocumented C functions).
Sure, we *could* pass Win32 calls to WINE (hoping they work), but that defeats the whole point of using.NET to be a truly cross platform development API. We might as well ditch Mono and just focus on getting the Microsoft.NET runtime to work over WINE by your philosophy.
Native function calls and Avalon pose a major problem in having applications developed with only Windows in mind working on Linux. Of course Linux developers can still benefit from using.NET for themselves, but the dream of "write once, run everywhere" is at risk if using native calls and Avalon becomes norm rather than the exception.
Slashdot Mirror
I don't got mail, I don't got mail, I don't got mail... Yaaaaayyy!
Unless they rewritten wine in c++ its going to have problems emulating c++ features like objects really really bad. I am not bashing C, but rather pointing out that rewriting the language to mimick an operating system heavily built on C++ is a mistake.
.NET). Things like MFC and .NET Forms are built on top of the Windows API. The only "core" Windows API that I know of uses C++ is GDI+ which was written as a newer and better version of the GDI (which may or may not be built on top of GDI and some undocumented C functions).
Huh? The Windows API is written almost entirely in C (it dates back to the mid 80's). New Windows features are still exposed through C (though I think some of the Vista features are only going to be exposed through
Sure, we *could* pass Win32 calls to WINE (hoping they work), but that defeats the whole point of using .NET to be a truly cross platform development API. We might as well ditch Mono and just focus on getting the Microsoft .NET runtime to work over WINE by your philosophy.
.NET for themselves, but the dream of "write once, run everywhere" is at risk if using native calls and Avalon becomes norm rather than the exception.
Native function calls and Avalon pose a major problem in having applications developed with only Windows in mind working on Linux. Of course Linux developers can still benefit from using