Re: Member Variables Naming Convention

Dave,

Absolutely. I mean, with C++, all strings should be wrapped in the _T()
macro and every run-time library routine and API appears to have both an
ASCII and Unicode version. Clearly, the .NET designers wanted to clean
things up a little and, presumably, thought simple names were cleaner
than all this Hungarian notation, etc.

Hungarian notation isn't completely outlawed, however :)

Actually, in the Microsoft guidelines, it really is.

I see no mention in the standards about the use of "txtFirstName", for
example, and I try to use this notation when I need to distinguish between
controls that would otherwise have identical names, such as,
"lblFirstName". Standardized prefixes are desirable, but I can live
without them.

Reference to controls is a bit different that straight variables. I haven't
see what the guidelines say about that.

Yeah, I can't do it. One thing (of many things) that annoy me about .NET
is the verboseness. Having suffered from carpel-tunnel issues from time
to time, I'm not going to prefix every occurrance of a member variable
with five additional characters. I guess that is as good as any argument
for me to adopt the "_" prefix as my personal style.

Not every occurrence of a member variable.

I think consistency is important. Using the this. prefix only some of the
time could get you into trouble.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com


.

Relevant Pages

  • Re: To Hungarian or not to Hungarian
    ... standard found at: ... The argument was "Hungarian notation is no longer the recommended practice". ... The prefix should either be 2 or 3 characters long. ... Counter variables can be i,j,k but anything else gets a word - TempString, IsEmpty, AnimalType. ...
    (borland.public.delphi.non-technical)
  • Re: Member Variables Naming Convention
    ... Actually, in the Microsoft guidelines, it really is. ... Hungarian notation isn't completely outlawed, ... this notation when I need to distinguish between controls that would otherwise have identical ... Having suffered from carpel-tunnel issues from time to time, I'm not going to prefix every ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Questions about components naming convention
    ... Should I use the same prefix for components which have the ... hungarian notation is not necessary as long as you give your variables ... TeamBUG support for UK-BUG ...
    (borland.public.delphi.language.objectpascal)
  • Re: Member Variables Naming Convention
    ... references to controls a bit different than straight variables. ... Actually, in the Microsoft guidelines, it really is. ... Hungarian notation isn't completely outlawed, ... any argument for me to adopt the "_" prefix as my personal style. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Another newbie question
    ... Actually these days the most common emphasis I see is on meaningful names, ... real-world situations you will discover that 'hungarian notation' is equally ... Right, but if you read what Joel suggested, you can see how even the naming he suggests becomes wrong in a strongly typed system. ... Now if instead you create a unsafe string type, then the naming prefix is meaningless, the behavior that the "us" was meant to relay is encapsulated inside the type. ...
    (microsoft.public.vb.general.discussion)
Loading