Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
CLR and VFP
Message
De
31/08/2000 04:25:39
 
 
À
30/08/2000 12:19:13
Walter Meester
HoogkarspelPays-Bas
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00409695
Message ID:
00411186
Vues:
24
Walter,

>> Performance DML actions such as SQL SELECT, REPLACE, INSERT etc, heavely
>> rely on I/O etc. Since interpreting a single DML command would take a
>> fraction of the time to execute the underlying C/C++ code I won't expect any
>> benefit if the P-CODE was translated into native code.

I don't understand how interpreting then executing can be faster than native execution, please explain?

>> As for commands that don't rely that much on I/O, they could be faster if
>> compiled native code, but I doubt if that would be that much. Remember we've
>> got very fast string manipulation which is comparable to native compiled
>> code.

Wasn't their a comparison/test over at DevX on string manipulation in languages? Again if there was no real benifit in compilation to native code why do it? The new CLR has JIT compilers that convert the IL to native code? Why does Microsoft spend thousands of dollars in compiler development?

>> The speed of my application are mostly determined by I/O, so I won't expect
>> very much speed enhancement with a native compiler.

So your software has no analytic functions, logic, control statements or interface?

>> You don't have to. When reading the ASCII and comparing this with a FPW 2.6
>> app, you come to this conclusion real fast.

How can you draw this conclusion by viewing the P-Code through Notepad? Can you categorically say that you understand what its composed of? I am not on the VFP development team so I can't but again their are design tradeoffs, speed VS size etc.

>> Well, I read some story about one exe containing several megs of debuging
>> info because of commenting you're code. Developers should not be punished
>> for commenting code. Well it is not up to me to decided how the VFP team
>> would spend its time. Everyone has other priorities. Personally I like to
>> see that the VFP team expands its compiling options....

In debug builds granted but IMHO that's okay. Go build yourself a debug and release DLL in Visual C++ and look at the differences in size and speed? How are you being punished by including comments in the DEBUG versions of your code?
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform