Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
What does .NET do to a language?
Message
De
27/02/2001 13:53:56
 
 
À
27/02/2001 13:01:12
Jonathan Cochran
Alion Science and Technology
Maryland, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00479724
Message ID:
00480198
Vues:
39
Jonathan,

You are, however, quite correct that what you feared would in all eventuality come true. You would need to 'wrap' VFP's data access method somehow and as you suggested that would be the end of the product. If you did this you essentially remove VFP's speedy data access and hobble the product into extinction. Desktop, ISAM-based data access has no better champion than FoxPro. None whatsoever.

I remember a buddy of mine who tried to get an ASM (Assembly language) program to read some data out of a serial port many moons ago (FP 2.0) and told me he was quite surprised and impressed that FoxPro was faster, even in that case. "Why", I asked him, "do think this is the case?" He speculated that it was FoxPro's proprietary memory management that allowed it to use RAM rather than disk space and since he didn't want to build an equivilent in ASM <g> he went back to FP.

Now, ASM will in almost all cases be faster than VFP but when it comes to tossing data around on the desktop I'm not aware of anything better or faster. IMO we would lose this in a CLR-based world and that would, er, stink. <g>


>Thanks for clearing that up. I actually did read the beginning of the thread, but I guess I mis-read it. Someone had posted a link to a list of things that are changing (broken to some) in the next VB, and said that they hoped there wasn't a similar list for the next version of VFP. I guess I implied that Craig's two items were definite changes, not what would change if VFP went to the CLR.
>
>>Jonathan,
>>
>>>Maybe I've missed something, ...
>>
>>You just missed the beginning of the thread, where the context of the discussion was about what Foxpro would lose IF it were ported to the Common Language Runtime (CLR) of .NET.
>>
>>That is NOT happening, so don't panic! :-)
>>
>>>...is there any documentation or other discussion areas on this? Sorry for so many questions, but this is the first I've heard of any of this.
>>
>>http://fox.wikis.com/wc.dll?Wiki~ShouldVFPBeInTheCLR
>>http://fox.wikis.com/wc.dll?Wiki~ShouldVFPBeInVSDotNet
Best,


DD

A man is no fool who gives up that which he cannot keep for that which he cannot lose.
Everything I don't understand must be easy!
The difficulty of any task is measured by the capacity of the agent performing the work.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform