One-garian Notation
-
I too was a Hungarian convert. I too saw .NET and thought - is this not a step backwards? But then I relaxed a bit, and realized I do not look at listings much anymore - I use class diagrams; I use the IDE. I do not use paper. Both the class diagram and the IDE give you information on types, when you need them. I think the Hungarian has gone the way of the Arianism Apostasy, and am actually quite glad to see it go. At least you can read code now, without your eyes getting caught on a list of random seeming characters: "lpcivst" or similar in front of the words "UserNames". Mind you, I still use "tb" in front of text boxes, and "but" for buttons - but I never said I was consistent!
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
OriginalGriff wrote:
"but" for buttons
But, but, but... why not "btn"? ;P
OriginalGriff wrote:
"tb" in front of text boxes
I use "txt", but "tb" does make perfect sense too.
-
Beware all those who read the following, they are the irreverent ramblings of a heretic ... Religious beliefs are so tricky. For the true believer no alternatives can be possible. Their minds are closed. I was once a devout believer of Hungarian notation. Charles Simonyi was my guiding light. My strings were all szDecorated, and I was at peace with the world. But, as with all religions, there were those who would not accept the one true way. Hedonistic forces held sway at Microsoft, and .Net naming conventions repudiated Hungarian notation! I was thrown into confusion, and my world disintegrated around me! Had I been led astray? Were my beliefs really so faulty? All those years, for nothing? And then I noticed something incredibly suspect about the preachings of the anti-Hungarian notationalists. Despite their adamant claim that Hungarian notation was evil, they in reality espoused a corrupted form of Hungarian notation themselves! Yes, it is true, the anti-Hungarian notationalists are inconsistent! They call for the abolition of Hungarian notation, while preaching the following doctrine: - The names of interfaces must start with the letter I. - The names of types must start with the letter T. Why was this? How could they ask me to give up one faith for a new one that contradicted itself? And then one day my turmoil was resolved! In a moment of revelation the great nerd in the sky spoke to me: "Do not follow the preaching of others! Create your own religion, be true to yourself, and say to hell with the forces of conformity. It will be a rocky road, and you will be held in contempt, but you will discover an inner peace that not even Hungarian notation gave you." I call my new religion "one-garian notation". It can be considered to be a further development (or corruption, if you will) of the .Net naming conventions, where not just the names of interfaces and types have specific one-character prefixes, but the following as well: - The names of constants must start with the letter C. - The names of delegates must start with the letter D. - The names of enumerators must start with the letter E. That's it. One-garian notation (named because it is based on one-character prefixes) is the same as .Net naming conventions, plus the use of three additional one-character rules, for a total of
pI vThink aHungarian nNotation vIs iA aWonderful nThing cAnd pEveryone avShould vUse pIt aAll dThe nTime, adNo nMatter pWhat dThe nContext, adEven adWhen vSpeaking.
Cheers, Vikram. (Got my troika of CCCs!)
-
pI vThink aHungarian nNotation vIs iA aWonderful nThing cAnd pEveryone avShould vUse pIt aAll dThe nTime, adNo nMatter pWhat dThe nContext, adEven adWhen vSpeaking.
Cheers, Vikram. (Got my troika of CCCs!)
No puns for you anymore! ;P
xacc.ide
IronScheme - 1.0 RC 1 - out now!
((λ (x) `(,x ',x)) '(λ (x) `(,x ',x))) The Scheme Programming Language – Fourth Edition -
Beware all those who read the following, they are the irreverent ramblings of a heretic ... Religious beliefs are so tricky. For the true believer no alternatives can be possible. Their minds are closed. I was once a devout believer of Hungarian notation. Charles Simonyi was my guiding light. My strings were all szDecorated, and I was at peace with the world. But, as with all religions, there were those who would not accept the one true way. Hedonistic forces held sway at Microsoft, and .Net naming conventions repudiated Hungarian notation! I was thrown into confusion, and my world disintegrated around me! Had I been led astray? Were my beliefs really so faulty? All those years, for nothing? And then I noticed something incredibly suspect about the preachings of the anti-Hungarian notationalists. Despite their adamant claim that Hungarian notation was evil, they in reality espoused a corrupted form of Hungarian notation themselves! Yes, it is true, the anti-Hungarian notationalists are inconsistent! They call for the abolition of Hungarian notation, while preaching the following doctrine: - The names of interfaces must start with the letter I. - The names of types must start with the letter T. Why was this? How could they ask me to give up one faith for a new one that contradicted itself? And then one day my turmoil was resolved! In a moment of revelation the great nerd in the sky spoke to me: "Do not follow the preaching of others! Create your own religion, be true to yourself, and say to hell with the forces of conformity. It will be a rocky road, and you will be held in contempt, but you will discover an inner peace that not even Hungarian notation gave you." I call my new religion "one-garian notation". It can be considered to be a further development (or corruption, if you will) of the .Net naming conventions, where not just the names of interfaces and types have specific one-character prefixes, but the following as well: - The names of constants must start with the letter C. - The names of delegates must start with the letter D. - The names of enumerators must start with the letter E. That's it. One-garian notation (named because it is based on one-character prefixes) is the same as .Net naming conventions, plus the use of three additional one-character rules, for a total of
Funnily,
szDecoratedstrings are not what Charles Simonyi suggested. Unless that's a decorated size - See App vs. Sys Hungarian Notation. "Sys" has some use in pure C programming, with a limited set of base types and high variation in operator effects (mostly runtime validity) depending on the declared type. The main drawback of "App" is the multitude of types in modern programming. If we need two interfaces, a facade, a model and a controller to separate one bad thing into two good ones, you quickly run out of sensible prefixes.Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server.modified on Sunday, May 9, 2010 5:17 AM
-
pI vThink aHungarian nNotation vIs iA aWonderful nThing cAnd pEveryone avShould vUse pIt aAll dThe nTime, adNo nMatter pWhat dThe nContext, adEven adWhen vSpeaking.
Cheers, Vikram. (Got my troika of CCCs!)
I prefer the Hungarian version (and I don't speak Hungarian): "I Think magyar jelölés egy csodálatos dolog, és mindenkinek meg kell Használata ez állandóan, nem számít, milyen háttér, még akkor is szólva." (Google translate, but I am not to sure of the first bit. Babylon translated it to "True" which may be a comment, but wasn't really helpful)
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
OriginalGriff wrote:
"but" for buttons
But, but, but... why not "btn"? ;P
OriginalGriff wrote:
"tb" in front of text boxes
I use "txt", but "tb" does make perfect sense too.
aspdotnetdev wrote:
why not "btn"?
OriginalGriff wrote:
I never said I was consistent!
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
I prefer the Hungarian version (and I don't speak Hungarian): "I Think magyar jelölés egy csodálatos dolog, és mindenkinek meg kell Használata ez állandóan, nem számít, milyen háttér, még akkor is szólva." (Google translate, but I am not to sure of the first bit. Babylon translated it to "True" which may be a comment, but wasn't really helpful)
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
Ugyes vagy! [probably missed some accents but nem eldekel] The best 'Hungarian Notation' is 'Az Anyad' a greating bound to win friends and influence people.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
-
Beware all those who read the following, they are the irreverent ramblings of a heretic ... Religious beliefs are so tricky. For the true believer no alternatives can be possible. Their minds are closed. I was once a devout believer of Hungarian notation. Charles Simonyi was my guiding light. My strings were all szDecorated, and I was at peace with the world. But, as with all religions, there were those who would not accept the one true way. Hedonistic forces held sway at Microsoft, and .Net naming conventions repudiated Hungarian notation! I was thrown into confusion, and my world disintegrated around me! Had I been led astray? Were my beliefs really so faulty? All those years, for nothing? And then I noticed something incredibly suspect about the preachings of the anti-Hungarian notationalists. Despite their adamant claim that Hungarian notation was evil, they in reality espoused a corrupted form of Hungarian notation themselves! Yes, it is true, the anti-Hungarian notationalists are inconsistent! They call for the abolition of Hungarian notation, while preaching the following doctrine: - The names of interfaces must start with the letter I. - The names of types must start with the letter T. Why was this? How could they ask me to give up one faith for a new one that contradicted itself? And then one day my turmoil was resolved! In a moment of revelation the great nerd in the sky spoke to me: "Do not follow the preaching of others! Create your own religion, be true to yourself, and say to hell with the forces of conformity. It will be a rocky road, and you will be held in contempt, but you will discover an inner peace that not even Hungarian notation gave you." I call my new religion "one-garian notation". It can be considered to be a further development (or corruption, if you will) of the .Net naming conventions, where not just the names of interfaces and types have specific one-character prefixes, but the following as well: - The names of constants must start with the letter C. - The names of delegates must start with the letter D. - The names of enumerators must start with the letter E. That's it. One-garian notation (named because it is based on one-character prefixes) is the same as .Net naming conventions, plus the use of three additional one-character rules, for a total of
Wow, lots of comments! :) But I'd like to ask if anyone has any opinion regarding my suggesions, which I'm actually quite serious about, despite the humorous tone of my posting? - The names of constants must start with the letter C. - The names of delegates must start with the letter D. - The names of enumerators must start with the letter E. Justifications: - Previous standard for constants was THE_UPPERCASE_SCREAMING style, because constants are different. So I want to still emphasise that constants are different, and adding the C does that. - I often have a delegate declaration that is for a specific method, so it makes sense to use the name of the method with the D added to the front. - The use of enumerators often involves declaring a usage of the enumerator that naturally would have the same name as the enumerator itself, which isn't allowed. So by saying the enumerator name starts with E then the usage can have the same name without the E. Just like with INames for interfaces and TNames for types, these three things are sufficiently different from run-of-the-mill items that I like the idea of giving them special names.
-
Ugyes vagy! [probably missed some accents but nem eldekel] The best 'Hungarian Notation' is 'Az Anyad' a greating bound to win friends and influence people.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
I suspect that this will not win friends, but will influence people... :laugh: So in Gealic: Pogue mahone!
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
I suspect that this will not win friends, but will influence people... :laugh: So in Gealic: Pogue mahone!
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
OriginalGriff wrote:
So in Gealic: Pogue mahone!
Not even close. It's an inoquous phrase - literaly 'your mother' - but causes DEFCON2 offence. A bit like saying to a Cpian that they sound like CSS.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
-
aspdotnetdev wrote:
why not "btn"?
OriginalGriff wrote:
I never said I was consistent!
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
OriginalGriff wrote:
I never said I was consistent!
But you always say that!
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
-
Wow, lots of comments! :) But I'd like to ask if anyone has any opinion regarding my suggesions, which I'm actually quite serious about, despite the humorous tone of my posting? - The names of constants must start with the letter C. - The names of delegates must start with the letter D. - The names of enumerators must start with the letter E. Justifications: - Previous standard for constants was THE_UPPERCASE_SCREAMING style, because constants are different. So I want to still emphasise that constants are different, and adding the C does that. - I often have a delegate declaration that is for a specific method, so it makes sense to use the name of the method with the D added to the front. - The use of enumerators often involves declaring a usage of the enumerator that naturally would have the same name as the enumerator itself, which isn't allowed. So by saying the enumerator name starts with E then the usage can have the same name without the E. Just like with INames for interfaces and TNames for types, these three things are sufficiently different from run-of-the-mill items that I like the idea of giving them special names.
RenniePet wrote:
Previous standard for constants was THE_UPPERCASE_SCREAMING style, because constants are different
Why? How is a constant different from a property with no setter? From an enum value? (And yes I do know a property could do other things...)
RenniePet wrote:
it makes sense to use the name of the method with the D added to the front.
Again, why? If you have a delegate with only one method, why are you using a delegate? If you can have lots of methods assigned to a delegate, which one would you pick to use for the delegate name?
RenniePet wrote:
The use of enumerators often involves declaring a usage of the enumerator that naturally would have the same name as the enumerator itself, which isn't allowed.
It is in C#!
DownloaderReporting DownloaderReporting = 0; DownloaderReporting = DownloaderReporting.Normal;I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
OriginalGriff wrote:
So in Gealic: Pogue mahone!
Not even close. It's an inoquous phrase - literaly 'your mother' - but causes DEFCON2 offence. A bit like saying to a Cpian that they sound like CSS.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
When I saw the Google translation to "The Mother" I guessed it might just be a smidgen offensive... :laugh:
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
RenniePet wrote:
Previous standard for constants was THE_UPPERCASE_SCREAMING style, because constants are different
Why? How is a constant different from a property with no setter? From an enum value? (And yes I do know a property could do other things...)
RenniePet wrote:
it makes sense to use the name of the method with the D added to the front.
Again, why? If you have a delegate with only one method, why are you using a delegate? If you can have lots of methods assigned to a delegate, which one would you pick to use for the delegate name?
RenniePet wrote:
The use of enumerators often involves declaring a usage of the enumerator that naturally would have the same name as the enumerator itself, which isn't allowed.
It is in C#!
DownloaderReporting DownloaderReporting = 0; DownloaderReporting = DownloaderReporting.Normal;I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
OriginalGriff wrote:
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in.
Does that work?
Join the cool kids - Come fold with us[^]
It depends on how broadly written the court order is... :((
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
RenniePet wrote:
Previous standard for constants was THE_UPPERCASE_SCREAMING style, because constants are different
Why? How is a constant different from a property with no setter? From an enum value? (And yes I do know a property could do other things...)
RenniePet wrote:
it makes sense to use the name of the method with the D added to the front.
Again, why? If you have a delegate with only one method, why are you using a delegate? If you can have lots of methods assigned to a delegate, which one would you pick to use for the delegate name?
RenniePet wrote:
The use of enumerators often involves declaring a usage of the enumerator that naturally would have the same name as the enumerator itself, which isn't allowed.
It is in C#!
DownloaderReporting DownloaderReporting = 0; DownloaderReporting = DownloaderReporting.Normal;I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
That's just asking for a wet-kipper slap! :) I was going to suggest that itwould be better to camel the variable so:
DownloaderReporting downloaderReporting = 0;
downloaderReporting = DownloaderReporting.Normal;But then the property's still going to be:
DownloaderReporting DownloaderReporting { get { return this.downloaderReporting; } }
Either way, things'll go kaka quicker then you can even punch an MS employee's face.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
-
RenniePet wrote:
Previous standard for constants was THE_UPPERCASE_SCREAMING style, because constants are different
Why? How is a constant different from a property with no setter? From an enum value? (And yes I do know a property could do other things...)
RenniePet wrote:
it makes sense to use the name of the method with the D added to the front.
Again, why? If you have a delegate with only one method, why are you using a delegate? If you can have lots of methods assigned to a delegate, which one would you pick to use for the delegate name?
RenniePet wrote:
The use of enumerators often involves declaring a usage of the enumerator that naturally would have the same name as the enumerator itself, which isn't allowed.
It is in C#!
DownloaderReporting DownloaderReporting = 0; DownloaderReporting = DownloaderReporting.Normal;I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
Maybe I'm not explaining myself very well ... Here are some examples:
const string CServiceName = "Merlinia Process Manager"; private delegate void DProcessProcessHasStopped(IntPtr processHandle); private DProcessProcessHasStopped \_processProcessHasStopped; private void InitializeCrossThreadInvocation() { \_processProcessHasStopped = ProcessProcessHasStopped; } private void CT\_ProcessProcessHasStopped(IntPtr processHandle) { base.InvokeDelegate(\_processProcessHasStopped, processHandle); }This is part of a pattern in a class that supports cross-thread invocation of methods.
public enum EProcessStatus
{
ProcStopped,
ProcStarting, // Has been started, but has not reported "up and running"
ProcRunning,
ProcStopping // Has been signaled to stop, but not stopped yet
}public EProcessStatus ProcessStatus; -
It depends on how broadly written the court order is... :((
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
Find a target who travels. The joy of legal juristiction means that somewhere wont enforce the restraining order.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
-
Find a target who travels. The joy of legal juristiction means that somewhere wont enforce the restraining order.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
I bow to the expert in the field! Respect!
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
-
That's just asking for a wet-kipper slap! :) I was going to suggest that itwould be better to camel the variable so:
DownloaderReporting downloaderReporting = 0;
downloaderReporting = DownloaderReporting.Normal;But then the property's still going to be:
DownloaderReporting DownloaderReporting { get { return this.downloaderReporting; } }
Either way, things'll go kaka quicker then you can even punch an MS employee's face.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
Yes, normally I would camelCase it, but it was just an example to show it can be done in C#. Normally I would call it reportingReason or similar as I would consider it too confusing to use the enum name as the name for an instance of that enum - it would be like saying
string string = "string";
and expecting no-one to laugh at you...
I have learnt that you can not make someone love you, all you can do is stalk them and hope they panic and give in. Apathy Error: Don't bother striking any key.
