Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Whats bad about Visual Foxpro
Message
De
17/07/2001 17:30:59
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., Nouvelle Zélande
 
 
À
17/07/2001 03:22:28
Gerry Schmitz
GHS Automation Inc.
Calgary, Alberta, Canada
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00530878
Message ID:
00531769
Vues:
26
Gerry

>>If there is actual machine code being produced at runtime (which is subsequently executed by the "processor"), then that would be a "compiler" (and not an interpreter). More precisely, it would be a JIT Compiler, or "Just-In-Time" Compiler.<<

One might argue that a VFP p-code "interpreter" also converts p-code to a sequence of "machine code" routines that get run at runtime.

I'm not trying to start an IT purity "war" here. Certainly FP apps have been "compiled" to p-code for a long time.

As far as I am concerned, it doesn't matter whether the thing is "compiled" or "interpreted" as long as the system yields acceptable performance/resource requirement. VFP does that.

Regards

JR
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us.
"
-- Shakespeare: Coriolanus, Act 1, scene 1
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform