Hi Walter

Thanks for answering ... for Jim.

>Hi terry,
>
>Sigh ... here we go again.

Why sigh? Have I asked before?

>>What have you gained from missing out "ln" or "lc"?
>
>I could anwer with the question. What do you gain with ?? Well, I know the argument about knowing the type in preventing mistakes, but in most cases, it just does not cut it. I rarely come across a circumstance where I cannot determine the type of a variable and I desperately need to know. You might be right in theory, but in practise it is just not worth it.

Not WORTH typing in "lc" or "ln" at beginning? SO much effort! I presume you haven't had to maintain someone's prog where they have the line like:

ttime = MyFile.Time

From that you can determine:
1) that MyFile.Time is a 4-char field and not DateTime
2) ttime is meant to be char and not DateTime
3) where the hell ttime came from (not declared in the current proc, no "g" to show it's global, so no knowing if it's just been created on-the-fly, in the above line, or already has a value from somewhere else)?

>
>>personal rule being the operative expression! Surely Hungarian is to get round people's personal prefs and make everything more universally understandable.
>
>You could not be more wrong here. Do you happen to know the complete hungarian notation. What its inmediate purpose was. How it is to be ported to the VFP platform ? Do the same motivations and rules apply to the VFP platform ?? How many versions of hungarian notations are out there ??
>
>There is simply *no* one standard for hungarian notation on the VFP platform.

I thought we were talking about H Not. as applied to VFP recommended naming conventions here. Hell, I wasn't even aware of the term before joining the UT.

>
>>>Man, if they can't sniff that out they probably should find another job.
>>
>>Why put them through the trouble of having to sniff, when they could just use their eyesight? And if you've ever had to maintain someone else's code and cursed them for their short-comings, foibles, weird personal structures, etc., have you ever said that to yourself.
>
>Because hungarian notation bring problems in readability also (lnAccountNumber can be easily read as In - Acount Number, and confuse people. No matter how hardcode programmer you are, you can read plain english way easier than hungarian notation and therefore at least my brain can get confused with hungarian notation).

But if you're adhering to HN then there WON'T BE any vars beginning with "In" (either "gn" or "ln" or, if wishing to distinguish between float and integer, maybe "li")

>
>>>Even if I did 'document' it, they'd likely not have it at hand.
>
>>Even more reason for going Hungarian, I'd say.
>
>I agree with Jim, If they cannot find out by looking at the code, they should be looking for another job. It is knit picking. Esspecially since we are able to specify the type of a variable in code (eg. LOCAL MyVar as Char)

Sorry but that's bol**cks". Just cos you'tre good at the job doesn't mean you should have to strive when reading someone else's mess. See my example above.

Terry

BTW "It is knit picking." refers to the eggs of lice, as in "nit picking" - just to be nit-picking! :-)
>