Skip to main content
Software Engineering

Timeline for What is the benefit of not using Hungarian notation?

Current License: CC BY-SA 3.0

38 events
when toggle format what by license comment
Apr 14, 2023 at 0:07 comment added Nick Alexeev Hungarian notation gets in the way of refactoring. Some refactorings involve a change of variable types which would require change of the Hungarian variable names. Change of variable names wouldn't be required without Hungarian. I think that's the main reason why Hungarian fell out of use. A contributing factor is the IDEs which provide type and scope information on the fly. More on that here.
Aug 17, 2018 at 10:55 comment added Error - CPU Not Foud @ArseniMourzenko - same for Delphi (and many other languages that come whit a DECENT IDE).
Apr 19, 2017 at 20:08 review Close votes
Apr 24, 2017 at 3:03
Jun 3, 2014 at 12:24 history protected Bart van Ingen Schenau
Jan 18, 2012 at 1:02 comment added yrk If there would be a strong reason behind encoding variable type in its name, there would be languages/preprocessor which enforce this convention. And, yes, it's stands like a bad typography.
Aug 26, 2011 at 18:03 answer added Ed Staub timeline score: 1
S Aug 22, 2011 at 23:30 answer added user unknown timeline score: 2
S Aug 22, 2011 at 23:30 history made wiki Post Made Community Wiki by user unknown
Aug 22, 2011 at 18:17 answer added Orclev timeline score: 7
Aug 22, 2011 at 18:05 answer added Kyralessa timeline score: 1
Aug 22, 2011 at 16:49 comment added Robert S. The logic is not quite the same. While the I prefix is from Hungarian notation, the reason behind using the I actually has an explanation. stackoverflow.com/questions/222457/…
Aug 22, 2011 at 15:18 comment added Konrad Morawski @Robert S. Hungarian notation is a convention - one that is (mostly) out of use, not recommended, deprecated etc. - but still it is one. What I'm pointing out is that the logic behind naming all interfaces "I-something" is essentially the same as the one behind Hungarian notation. So I'm wondering why we're supporting one while opposing the other. What's so special about interfaces. That's just inconsistent.
Aug 22, 2011 at 15:03 comment added Robert S. Well, that's the thing: Hungarian notation is not the convention. It may have been in the past, but it's not anymore. Take a look at the .NET Framework source, sample apps posted on popular .NET blogs, generated code in Visual Studio, etc. We could agree that all strings should be prefixed with str, but as you can see in the answers to the question, that's not what people want.
Aug 22, 2011 at 14:32 comment added Konrad Morawski @Robert S. I know it's a convention - so is Hungarian notation. My point is that a language being strongly-typed and an IDE showing you what is what on-the-fly aren't in themselves sufficient reasons not to use such prefixes; apparently. So if we agree that ISomething convention is somehow justified, we cannot base our argument against Hungarian notation on these reasons alone.
Aug 22, 2011 at 14:22 comment added Sean Patrick Floyd what is the benefit of not using Hungarian notation "Not being hated by your co-workers" comes to mind ...
Aug 22, 2011 at 13:58 comment added Robert S. The I prefix on interfaces is a convention adopted by the .NET community.
Aug 22, 2011 at 12:41 answer added Wayne Molina timeline score: 16
Aug 22, 2011 at 10:08 comment added Konrad Morawski @MainMa What else is prefixing interface names with I (in .NET) if not Hungarian notation, and its supposedly worst kind? Won't Visual Studio reveal to you that Something is an interface? It will. And yet we still name interfaces ISomething.
Aug 22, 2011 at 4:11 comment added kevin cline "When projects get extensive"... should not matter. There should only be a small number of variables in scope at any point: a handful of class variables, and another handful of method arguments. If you can't keep them straight, then the class is too big or the method is too long. Hungarian notation was invented for Windows C programming, basically as a work-around for the horrible Windows API. Nothing similar was ever suggested or wanted for Unix development.
Aug 22, 2011 at 3:15 vote accept Community Bot moved from User.Id=29981 by developer User.Id=102
Aug 22, 2011 at 2:23 comment added Rei Miyasaka @MainMa I'm not sure that's a good reason not to know the type of a value in PHP.
Aug 22, 2011 at 2:20 answer added ZJR timeline score: 3
Aug 21, 2011 at 23:38 answer added Oqaqiq timeline score: 3
Aug 21, 2011 at 20:57 answer added Saeed Neamati timeline score: 6
Aug 21, 2011 at 20:48 answer added Longpoke timeline score: 4
Aug 21, 2011 at 20:45 answer added BillThor timeline score: 2
Aug 21, 2011 at 20:01 history edited user8 CC BY-SA 3.0
rewrote title as a question
S Aug 21, 2011 at 20:01 history suggested Mike Partridge CC BY-SA 3.0
rewrote title as a question
Aug 21, 2011 at 19:49 review Suggested edits
S Aug 21, 2011 at 20:01
Aug 21, 2011 at 18:40 history tweeted twitter.com/#!/StackProgrammer/status/105348616486518784
Aug 21, 2011 at 17:53 comment added Arseni Mourzenko What language/IDE do you use? In Visual Studio, you don't have to go to the definition to know the type of a variable, since the IDE gives it to you. In languages where types are not enforced, like PHP, you don't need to know the type most of the time (since you can assign 0 or 1 to a boolean).
Aug 21, 2011 at 17:44 answer added tsundoku timeline score: 19
Aug 21, 2011 at 17:11 answer added JeffO timeline score: 14
Aug 21, 2011 at 16:43 answer added user7519 timeline score: 83
Aug 21, 2011 at 16:36 answer added Falcon timeline score: 55
Aug 21, 2011 at 16:31 answer added ratchet freak timeline score: 2
Aug 21, 2011 at 16:27 answer added Marjan Venema timeline score: 158
Aug 21, 2011 at 16:13 history asked user29981 CC BY-SA 3.0
toggle format

AltStyle によって変換されたページ (->オリジナル) /