Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Whats bad about Visual Foxpro
Message
De
16/07/2001 11:02:03
 
 
À
16/07/2001 10:55:53
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivie
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00530878
Message ID:
00531012
Vues:
26
>>>1) Often you only get an error message at runtime. It helps to develop better programs if errors appear already when you compile a program.
>>
>>Can you provide an example?
>
>Access any un-initialized variable, e.g.:
>
>
>x = y
>
>
>If you didn't declare "y" previously, a compiler would protest at compile-time.

That's not interpreted. Under a language that allows strict typing, the compiler would complain. VB allows both.

>
>>Even "real" compilers have to look up the variable.
>
>I understand that a compiler would convert a variable reference, like "x" or "y", to the address (number) in RAM. No lookup is done at runtime.

Yes, it is. It still has to lookup the address.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform