Hi > I think it increases maintenance *not* to use hungarian notation. > It makes you constantly have to look up "what type is this variable" > instead of having it right there before you. For instance, when I > write a TRACE statement I can see right away whether to put %d or > %f or whatever.
Well, if you keep your functions small so that you don't need to scroll to see paramters then this isn't a problem. Obviously it's different for member varaibles. The name of the variable and its context should make it clear what type it is. > If your variable type changes, you do a find a replace, no big deal. As long as it works and doesn't change something you don't expect. > You still need to look up everywhere that it's used to make sure it's > being used correctly, no matter how you named it. That's what the compiler and your unit tests are for. > And as far as "ugly"... around here they made a rule "don't use > hungarian notation" and instead we have to write variables like > this: > list_pointer > stack_records_pointer > valid_boolean This is replacing one notation with another. > talk about ugly! And so much typing! If you're working with MFC you > have to be able to recognize Microsoft's hungarian notation, anyway, > so just get used to it and then it's not ugly anymore. You don't have to recognise anything. It's just another varaible name. Still ugly. Regards Paul Paul Grenyer email: [EMAIL PROTECTED] web: http://www.paulgrenyer.co.uk articles: http://www.paulgrenyer.dyndns.org/articles/ "15 miles to the love shack...." _______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
