That is if the VFP community desires the CLR or Common Language Runtime. What do you think Vlad? It is so eearly any opinion is really premature but there will still be difference between VB, VC++, VFP etc?
First of all, I don't think MS will listen to VFP community much, because you always have option to use older versions of VFP without CLR, that work great ad will work great long time.
Are there will be differences?
Yes and no. Language still be VB, C# or VFP or whatever MS will add in future. But all of them will be compiled into the same kind of code and will run with the same run-time libraries. I suppose these run-time libraries will be provided by MS with next version of MS Windows, so no more mess with installing them on each client computer.
This cause some common logic for all these languages. For example, next version of VB will have full-hierarchy classes, some obsolete statements will be removed, some new things will be added that moves VB somewhat towards VFP, logically. On the other side, VFP will be changed dramatically, and this is the worst thing cause a lot of discussions last time. For example, nobody beleives CLR will be able to work with native VFP tables. Also, it is obvious, that VFP speed in working with strings, objects and arrays will be spoiled too, just because current VFP interpreter and memory model is too different than in VB or C#, and it is not compartible to existing COM+ model. Well, MS also can move C#/VB towards VFP, but nobody think that this could happen, too much work and too much changes.
However, there are good news too. The main purpose of CLR is to use it in COM+ objects together with ADO recordsets and support COM+ events with early binding. So, there is a little chanse that MS leave all VFP features and advantages, but, CLR for VFP will be used as option in the compiling - 'COM DLL with CLR code'. To compile to such code you will be restricted to use certain commands and structures, but will be able to use some new commands and structures. It seems the most obvious and simple way without much of damage for VFP, but who knows?
What Is CLR (Common Language Runtime)? It is not only common language. It is also tree-like interpreter code, that can be used by many ways:
1. Just run it using run-time libraries (like java code)
2. Compile it to the processor code of the machine where code is running.
And here are all nuts of the new technology. Your application now can work everywhere, on any OS and any processor. You just need 'plug in' to compile CLR code. Compilation of such code is quick, easy and effective because most work on the program sources parsing already done and all code is represented in tree-like form that is the most quick form for compiling/converting to any other code. This is good replacement of Java. It was discovered already so far ago (I don't know exactly, I learnet this technology ~year ago). And MS gonna use it as a challenge for Java.
Hope this helped. [sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]
First of all, I don't think MS will listen to VFP community much, because you always have option to use older versions of VFP without CLR, that work great ad will work great long time.
Are there will be differences?
Yes and no. Language still be VB, C# or VFP or whatever MS will add in future. But all of them will be compiled into the same kind of code and will run with the same run-time libraries. I suppose these run-time libraries will be provided by MS with next version of MS Windows, so no more mess with installing them on each client computer.
This cause some common logic for all these languages. For example, next version of VB will have full-hierarchy classes, some obsolete statements will be removed, some new things will be added that moves VB somewhat towards VFP, logically. On the other side, VFP will be changed dramatically, and this is the worst thing cause a lot of discussions last time. For example, nobody beleives CLR will be able to work with native VFP tables. Also, it is obvious, that VFP speed in working with strings, objects and arrays will be spoiled too, just because current VFP interpreter and memory model is too different than in VB or C#, and it is not compartible to existing COM+ model. Well, MS also can move C#/VB towards VFP, but nobody think that this could happen, too much work and too much changes.
However, there are good news too. The main purpose of CLR is to use it in COM+ objects together with ADO recordsets and support COM+ events with early binding. So, there is a little chanse that MS leave all VFP features and advantages, but, CLR for VFP will be used as option in the compiling - 'COM DLL with CLR code'. To compile to such code you will be restricted to use certain commands and structures, but will be able to use some new commands and structures. It seems the most obvious and simple way without much of damage for VFP, but who knows?
What Is CLR (Common Language Runtime)? It is not only common language. It is also tree-like interpreter code, that can be used by many ways:
1. Just run it using run-time libraries (like java code)
2. Compile it to the processor code of the machine where code is running.
And here are all nuts of the new technology. Your application now can work everywhere, on any OS and any processor. You just need 'plug in' to compile CLR code. Compilation of such code is quick, easy and effective because most work on the program sources parsing already done and all code is represented in tree-like form that is the most quick form for compiling/converting to any other code. This is good replacement of Java. It was discovered already so far ago (I don't know exactly, I learnet this technology ~year ago). And MS gonna use it as a challenge for Java.
Hope this helped. [sig]<p>Vlad Grynchyshyn<br><a href=mailto:vgryn@softserve.lviv.ua>vgryn@softserve.lviv.ua</a><br>[/sig]