Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Joel on Software
Message
From
17/05/2005 09:59:27
 
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
01014573
Message ID:
01014879
Views:
24
>>I don't use "Hungarian" but I have a simple personal rule for your example... your lnAccountNumber would be AccountNumber and you lcAccountNumber would be AccountNo.
>>
>>Works nicely for me.
>>
>>In general I prefer to type descriptive names than use prefixes.
>
>I would argue that Mike's variable names are more descriptive (and yours more ambiguous). If you work in a multi developer environment, the prefixes make a huge difference when reading someone else's code. Or even if you work by yourself and you revisit code from long ago. I've experienced both scenarios and when I started using hungarian it was a huge difference.

It all comes back to personal preference.
Of course I have (and do) work in a multi-programmer environment.
I use the 'standard' of the program at hand when revising, and use the 'shop standard' for new code. Most often that *has* been "Hungarian".

Currently the shop standards are minimal (but do exist) and, funnily enough, we all seem to be able to read each other's code. Thankfully this one does not involve "Hungarian".

I simply find "Hungarian" as recommended by MS (and CodeBook) for VFP to be very hard to read. Especially when some of the programmers are fond of using the "!" operator too.

Whatever works for you (or a group) is what should be used. I think you'd find that using long descriptive names would be far more productive in the longer run. Most people cite the extra typing as being too much and use "Hungarian" as the reason to not have to do that extra typing.

cheers
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform