Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Foxpro performance .vs. C program...
Message
From
18/06/1997 15:44:52
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00036664
Message ID:
00036861
Views:
31
James,

The story I heard about the evolution of C was a little different than what you suggest, but that is neither here nor there.

What is material is that C ultimately resolves down to Assembly (or, if you prefer, "machine" language") and VFP does the exact same thing except much of it starts out as VFP native code which is "interpreted" by that Assembly language (which starts its life out as C code).

Just adding to the discussion

Jim N

>>How big are your tables?
>>
>>How heavy are your calculations?
>>
>>Do not forget that FoxPro doesn't have a native compiler. C/C++ are real compilers. And compiled code is always faster than interpreted code.
>>
>>After all, FoxPro is written in C... :)
>>
>>Vlad
>>
>
>Also, one of the reasons C was originally developed was to write operating systems. Which means there was alot of time devoted to the optimization of C. One of the big points selling points of C (when it 1st came out) was that you could write an OS with less than 10,000 lines of assembly(I think it was 10,000). With C, they would also be able to create hash tables, which grows linear with the number of records. It is hard for anything to out preform a hash table.
>
>James
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform