>That's not interpreted. Under a language that allows strict typing, the compiler would complain. VB allows both.
I know. I was talking about Visual FoxPro "treating variables like an interpreter". Otherwise, VFP is compiled.
>
>>
>>>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.
Technically, this is correct. However, I think Visual FoxPro has to do the following to get variable "x":
1) Find RAM-location of variable "x" in a list of variables. This is the "lookup" i was referring to.
2) Fetch the variable from the location it found.
Step 1 is the slower of the two, and a compiler (i.e., one that treats variables as a compiler usually does) would only do step 2.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
