int foo(float durr)
if (durr < 1.0f)
for (int i=0; i<10; ++i)
resolt += durr;
Oh, you must use the waterfall model of development!
This is Hungarian notation:
uint rowOffset, colOffset;
float xPos, yPos;
long sizeBytes;This is not Hungarian notation; this is a MS bastardisation known as "systems Hungarian":
uint uiRow, uiCol;
float fx, fy;
long dwSize;Hungarian is good. MS Systems Hungarian is the one that is oft derided.
Oh good, you saved me the trouble of leaping to the real hungarian-notation's defense!
As an aside, both the original proper hungarian notation (also known as "Apps Hungarian") and the butchered version that stole the lime-light ("Systems Hungarian") were popularized at Microsoft - they deserve credit for both, not just the bad version.
Apps Hungarian, the good one, was used to good effect by the Microsoft application development team who worked on Microsoft Excel and Word.
Later, it spread and got confused in the Microsoft operating system development team, (hence, "Systems" Hungarian), where it later spread out via the API's documentation as the "good practice" that isn't.
At least, that's what I've heard. Wikipedia
says that the 'hungarian' part of the name comes from the skilled engineer who created it (while at Xerox) and promoted it in the application team when he worked at Microsoft.