Aktuelle Änderungen Printable View Änderungen Bearbeiten
DebuggingClojure > GarbageCollector > GarbageCollection > BicycleRepairMan > PythonIDEs > ConditionSystems > Conditions > InformationSchema > GarbageCollection > RecentChanges > IPython > YukihiroMatsumoto > TestDrivenClojure > MatthiasFelleisen > CheckedExceptions > Exceptions > HungarianNotationClear TrailA variable naming convention developed by Charles Simonyi at Microsoft.
In Hungarian, the types of variables are encoded into the name. For example, m_pszName would be a (m_) member variable of a class, that is a (p) pointer to an (sz) null-terminated string. Hungarian was originally developed to support C programming by providing visual cues to compensate for C's lax type checking.
In essence, the original article never advocated encoding the actual machine representation "type" into the name, but to encode the semantics that the "type" can not and does not give. Adding "p" to show something is a pointer is pointless, but when integers are used to encode rows and columns, prepending a "c" or "r" makes wrong code look wrong.
Every line of code can be inspected by itself, and if every line of code is correct, the entire body of code is correct.
I’m using the word kind on purpose, there, because Simonyi mistakenly used the word type in his paper, and generations of programmers misunderstood what he meant.