Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Microsoft's position on Visual FoxPro and .NET
Message
 
À
15/06/2004 07:58:10
Metin Emre
Ozcom Bilgisayar Ltd.
Istanbul, Turquie
Information générale
Forum:
Visual FoxPro
Catégorie:
Conférences & événements
Divers
Thread ID:
00908177
Message ID:
00914064
Vues:
46
>"... it will crash, but you will not be able to find that problem during compilation. ..."
>
>Java can't find some errors at compile time too. I'm sure C# not different.
>
>
>Problems about VFPs weakness type coding not a big issue for me but...
>
>But I have to say that; sometimes I can difficulty find errors on forms. It give me an error but not code seem. I have to delete object by object to find error... I don't know if C# have problems like that?

Not sure what you mean exactly? Are you saying that just because Java doesn't find certain errors during compilation, C# won't find them either?

Strong typing is one of those things, where at first it is hard to see the advantage, and even after using it for a while, it isn't all that spectacular, until you end up going back to a language like VFP, and you almost crap your pants for fear of things not working right without you ever knowing...

Markus




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

Click here to load this message in the networking platform