Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Microsoft's position on Visual FoxPro and .NET
Message
 
À
14/06/2004 16:09:25
Walter Meester
HoogkarspelPays-Bas
Information générale
Forum:
Visual FoxPro
Catégorie:
Conférences & événements
Divers
Thread ID:
00908177
Message ID:
00913641
Vues:
34
>Markus,
>
>>Your statement is technically incorrect.
>
>>The CLR is not a runtime interpreter. Instead, the CLR performs JIT compilations on the code before it is executed. In other words: The IL code is compiled before it runs into something that is very similar to native code, except that it does not have to do things like memory management.
>
>Not knowing the very details of it, AFAIK, the CLR is a type of interpreter (just like VFP use the pcode interpreter). I understand that there is a difference in the aspects that when it is translating into a lower level code, but still it is a engine that translates the high level instructions into highly efficient low level library of functions.
>
>Walter,

Well, as per that definition, even a C++ or an Assembly compiler is an "interpreter" as it interprets regular code and then compiles it. But that is probably just a matter of defining the term.

What is important is that the technical aspect is very different. In VFP for instance, we create pcode and the VFP runtime than interprets that pcode to execute it. In .NET on the other hand, IL gets JIT compiled into machine code. From a compiler point of view, as well as runtime performance, this is a huge difference.

Markus




Markus Egger
President, EPS Software Corp
Author, Advanced Object Oriented Programming with VFP6
Publisher, CoDe Magazine
Microsoft MVP since 1995
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform