New Variable Naming Standards
-
That reminds me of something: Each player gets six cards, except for the player on the dealer's right, who gets seven. The second card is turned up, except on Tuesdays. Two jacks are a "half-fizzbin". If you have a half-fizzbin: a third jack is a "shralk" and results in disqualification; one wants a king and a deuce, except at night, when one wants a queen and a four; if a king had been dealt, the player would get another card, except when it is dark, in which case he'd have to give it back. The top hand is a "royal fizzbin", but the odds against getting one are said to be "astronomical".
At least artificial intelligence already is superior to natural stupidity
Yet again proving how knowledge of Star Trek can be invaluable in real life
-
I'd like to recommend some new variable namig standards. For this tutorial I'll use an example pulled from one of my recent projects. intValReCoRDCouNT1rjt 1: The first 3 letters are the type. 2: The second 3 letters are if it's a reference or value type. 3: The third set of letters - all capital letters (except for vowels) - is the name. 4: The numeric digit is what I usually vote on all of Dalek Dave's posts. 5: My initials (so we know what programmer made the variable). The great thing about these variable names is that they also work well as passwords. I call it Code Project Notation.
-
Yet again proving how knowledge of Star Trek can be invaluable in real life
-
I'd like to recommend some new variable namig standards. For this tutorial I'll use an example pulled from one of my recent projects. intValReCoRDCouNT1rjt 1: The first 3 letters are the type. 2: The second 3 letters are if it's a reference or value type. 3: The third set of letters - all capital letters (except for vowels) - is the name. 4: The numeric digit is what I usually vote on all of Dalek Dave's posts. 5: My initials (so we know what programmer made the variable). The great thing about these variable names is that they also work well as passwords. I call it Code Project Notation.
Two man enter, one man leave.
"the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011)
"No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011) "It is the celestial scrotum of good luck!" - Nagy Vilmos (2011) "But you probably have the smoothest scrotum of any grown man" - Pete O'Hanlon (2012) -
I'd like to recommend some new variable namig standards. For this tutorial I'll use an example pulled from one of my recent projects. intValReCoRDCouNT1rjt 1: The first 3 letters are the type. 2: The second 3 letters are if it's a reference or value type. 3: The third set of letters - all capital letters (except for vowels) - is the name. 4: The numeric digit is what I usually vote on all of Dalek Dave's posts. 5: My initials (so we know what programmer made the variable). The great thing about these variable names is that they also work well as passwords. I call it Code Project Notation.
MehGerbil wrote:
intValReCoRDCouNT1rjt1998
In which year variable was created. :rolleyes:
Regards, Hiren. -"I don't know, I don't care, and it doesn't make any difference".
-
MehGerbil wrote:
intValReCoRDCouNT1rjt1998
In which year variable was created. :rolleyes:
Regards, Hiren. -"I don't know, I don't care, and it doesn't make any difference".
-
Let's reduce it to the two digit year to save space. After all, including the century digits is redundant. :-D
^ I think I've identified our resident century digit hater.
-
I'd like to recommend some new variable namig standards. For this tutorial I'll use an example pulled from one of my recent projects. intValReCoRDCouNT1rjt 1: The first 3 letters are the type. 2: The second 3 letters are if it's a reference or value type. 3: The third set of letters - all capital letters (except for vowels) - is the name. 4: The numeric digit is what I usually vote on all of Dalek Dave's posts. 5: My initials (so we know what programmer made the variable). The great thing about these variable names is that they also work well as passwords. I call it Code Project Notation.
-
Let's reduce it to the two digit year to save space. After all, including the century digits is redundant. :-D
Let's reduce it to the two digit year to save space. That's what they said before they knew better...
regards Torsten When I'm not working
-
I'd like to recommend some new variable namig standards. For this tutorial I'll use an example pulled from one of my recent projects. intValReCoRDCouNT1rjt 1: The first 3 letters are the type. 2: The second 3 letters are if it's a reference or value type. 3: The third set of letters - all capital letters (except for vowels) - is the name. 4: The numeric digit is what I usually vote on all of Dalek Dave's posts. 5: My initials (so we know what programmer made the variable). The great thing about these variable names is that they also work well as passwords. I call it Code Project Notation.
I'd like to add a prefix m_ for member variables:
m_intValReCoRDCouNT1rjtto add a bit more security we should make the naming longer - one never knows, the name might already been taken.regards Torsten When I'm not working
-
MehGerbil wrote:
intValReCoRDCouNT1rjt1998
In which year variable was created. :rolleyes:
Regards, Hiren. -"I don't know, I don't care, and it doesn't make any difference".
Excellent! +52012mwh
VS2010/Atmel Studio 6.0 ToDo Manager Extension
Version 3.0 now available. There is no place like 127.0.0.1 -
I'd like to recommend some new variable namig standards. For this tutorial I'll use an example pulled from one of my recent projects. intValReCoRDCouNT1rjt 1: The first 3 letters are the type. 2: The second 3 letters are if it's a reference or value type. 3: The third set of letters - all capital letters (except for vowels) - is the name. 4: The numeric digit is what I usually vote on all of Dalek Dave's posts. 5: My initials (so we know what programmer made the variable). The great thing about these variable names is that they also work well as passwords. I call it Code Project Notation.
-
Let's reduce it to the two digit year to save space. After all, including the century digits is redundant. :-D
Will it not lead to the Y0.1K problem, like the Year 2000 problem?
-
I'd like to recommend some new variable namig standards. For this tutorial I'll use an example pulled from one of my recent projects. intValReCoRDCouNT1rjt 1: The first 3 letters are the type. 2: The second 3 letters are if it's a reference or value type. 3: The third set of letters - all capital letters (except for vowels) - is the name. 4: The numeric digit is what I usually vote on all of Dalek Dave's posts. 5: My initials (so we know what programmer made the variable). The great thing about these variable names is that they also work well as passwords. I call it Code Project Notation.
-
I'd like to recommend some new variable namig standards. For this tutorial I'll use an example pulled from one of my recent projects. intValReCoRDCouNT1rjt 1: The first 3 letters are the type. 2: The second 3 letters are if it's a reference or value type. 3: The third set of letters - all capital letters (except for vowels) - is the name. 4: The numeric digit is what I usually vote on all of Dalek Dave's posts. 5: My initials (so we know what programmer made the variable). The great thing about these variable names is that they also work well as passwords. I call it Code Project Notation.
I can go with 1, 2, 4, and five - silly, but I can imagine a tortured, past-plagued mind coming up with perfectly fine reasons. I'm curious, though, what's the motivation behind the casing rule of 3. They didn't want to shell out for an obfuscator?
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
Sure. I usually solve problems by wrapping them up in a warp field and keeping the antimatter contained. I only wish I had Kirk's ability to talk computers to death.
At least artificial intelligence already is superior to natural stupidity
-
Let's reduce it to the two digit year to save space. That's what they said before they knew better...
regards Torsten When I'm not working
-
I can go with 1, 2, 4, and five - silly, but I can imagine a tortured, past-plagued mind coming up with perfectly fine reasons. I'm curious, though, what's the motivation behind the casing rule of 3. They didn't want to shell out for an obfuscator?
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy
