>Alejandro,
>
>>>Here's an interesting piece :)
>>>
>>>Making Wrong Code Look Wrong - http://www.joelonsoftware.com/articles/Wrong.html
>>
>>I'd like to know why anyone would consider Hungarian = Bad. Hungarian may be unnecessary if the language is strongly typed, but it's not *bad*.
>
>Hungarian notation was invented for the C programming language. It has its great value in strong (strict) typed languages has you carefully have to match types. In weak (dynamic) typed languages it is less important, casting from double to int to numeric is done automatically: there is less need to be aware of the exact type. In VFP we have only: character, boolean, numeric, date, datetime and object as base types. Therefore there is less technical need to distinguis between derived types like int, float, double and memo and text.
>
>Walter,

If you read Charles Simonyi's original article outlining Hungarian Notation, you notice that he wasn't really stating that the data type was to be expressed . He used "type" in a more general way. Joel's article was interesting.

I still find it handy using it in the scope+type way that I thought it was meant to be used.