> You gave me two variable names. That was it. Even stupid employers > would give me more.
I think Jason was just trying to put you in the same situation where he (or his colleagues) had to debug that code, and figure what's wrong. Jason, this is one of the reasons why warning level 4 is helpful. It may catch such stuff... > Unless it was wrong. It's not unusual for a type to get changed and > for its name not to get updated. That is half my point. Is that reason enough to put aside HN then? Namespaces (just like any other thing in life) can be misused/abused as well. BTW, I personally neither love HN nor hate it, so please don't take this personally. But I can't still digest what's the relation of HN and namespaces, and in what cases can namespaces do the work of HN, and the other way round. And I think /dev's strategy to put something in the name of global variables to distinguish them from the rest and make sure everyone is aware of their globalness right away is A Good Thing (TM). At least it helps control the bad results of using global variables, no matter what you call it, HN or /N (the latter stands for /dev's notation!). ------------- Ehsan Akhgari Farda Technology (http://www.farda-tech.com/) List Owner: [email protected] [ Email: [EMAIL PROTECTED] ] [ WWW: http://www.beginthread.com/Ehsan ] If flying is safe, why is the airport called the terminal? _______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
