@Flameduck
And, well, a SML compiled binary is never executed. It is re-compiled by the MSIL compiler TO A NATIVE BINARY just before it is runned. so at this point they are equaly fast, but the fact that a .net binary is compiled in the computer where it is executed, enables the inclussion of some CPU speciffic optimizations that are not possible in a statically compiled traditional binary, unless there are some checks made before (and increasing the size of the final executable). That makes the binarys of .net runnable from a MacOsX or Linux system also, without having to create a final static executable.
A JIT (just in time) is a debuger,not a kind of compiled binary.
Most of them. BLIde as instance. the framework is powerfull enought to make hardly everything you can imagine. Most (not to say all) of the windows APIs have their corresponding method or even class in the .net framework. And in addition, they are organized and put together in a OO mode. the MSIL compiler translates this, not at run time, but just before run time, to the appropiate APIs of the OS where the application is running. (In case the APIs are not written directly on .NET, then there is no matching API to call, the code is executed directly increasing speed)
Just to enlighten us. Which .NET? 1.1? 2.0? 3.0?
.net 3.0 is compatible 100% with 2.0, in fact, it is 2.0 with the winFx AddOn. it is absolutely backwards compatible. will it be better to support DIRECTLY the .net, and take profit of the .NET run-time compiling? the answer is obviously YES.
Postulate. Why is the answer obviously yes? It doesn't seem particularly obvious to me.
It will be better becouse it will not be wrapped by a 'compatibility dll' based system that, in fact, calls the .net framework. so it is faster.Postulate. Why is the answer obviously yes? It doesn't seem particularly obvious to me.
Which I'm sure is nice for the 20 or so people who have Vista. For everyone using XP SP2 the answer is YES, and for everyone using anything else the answer is go fuck yourselves.
well, I thought we were talking about the future of BlitzMax, not the present. I don't know much people that uses still Windows 95 wich is not supported by BlitzMax. So I assume windows users will be using vista in a not so far future. By the way, MacOsX supports XWindows, wich is the basis for MONO... Well Neverwinter Nights 2 certainly is. Please elaborate under what possible scenario a JIT compiled binary is ever faster than a natively compiled one.
copared to what? is there any non .net version to compare it?And, well, a SML compiled binary is never executed. It is re-compiled by the MSIL compiler TO A NATIVE BINARY just before it is runned. so at this point they are equaly fast, but the fact that a .net binary is compiled in the computer where it is executed, enables the inclussion of some CPU speciffic optimizations that are not possible in a statically compiled traditional binary, unless there are some checks made before (and increasing the size of the final executable). That makes the binarys of .net runnable from a MacOsX or Linux system also, without having to create a final static executable.
A JIT (just in time) is a debuger,not a kind of compiled binary.
It covers 100% of the .net 1.1 framework, and it is being improved to cover .net 2.0 in a few months.
Which is absolutely useless as Vista ships with 3.0 and like 2.0 it is not immediately backwards compatible.
That's not true. .net 3.0 i .net 2.0 plus WinFx and it is 100% backwards compatible. (By the way, .net 2.0 was backwards compatible too, except for the network class, that was changed to be even more secure. most of the .net 1.1 applications can be run under .net 2.0 without any change)Which is absolutely useless as Vista ships with 3.0 and like 2.0 it is not immediately backwards compatible.
What application could you possibly write in .Net that doesn't use specific API calls?
Most of them. BLIde as instance. the framework is powerfull enought to make hardly everything you can imagine. Most (not to say all) of the windows APIs have their corresponding method or even class in the .net framework. And in addition, they are organized and put together in a OO mode. the MSIL compiler translates this, not at run time, but just before run time, to the appropiate APIs of the OS where the application is running. (In case the APIs are not written directly on .NET, then there is no matching API to call, the code is executed directly increasing speed)
I think Java is a better bet. Not only has it been out longer (and thus more throughly tested), it's also more widely adapted.
Well actually I think BlitzMAX should keep generating native code as long as humanly possible. I'd rather have a cross compiler than a .Net one.
Well... just to clarify that Java is intepreted and .net is compiled, the same as BlitzMax... By the way, .net is also cross platform...Well actually I think BlitzMAX should keep generating native code as long as humanly possible. I'd rather have a cross compiler than a .Net one.
So when are we getting blide for Linux and Mac then? If it's as simple as you seem to indicate that wouldn't be difficult at all, would it?
As soon as windows version gets stable and MONO 2.0 is released I will begin the beta testing process. (By the way, I will need some help).