At 800 mhz, I stopped worrying about most of this stuff. It's "perception" that is important.

And, when it came to writing "converters", that little "m." also made it a lot easier for me to parse my code. You're viewing it in one (limited) context; it serves other purposes that may have nothing to do with the actual running of the program.

It gets even sillier when you consider that in most programs, there are many "performance blunders" that make the use of "m." insignificant, even in YOUR programs; eg. one "misplaced" LOCAL will create a lot more overhead than a couple of m&m's.

I expect that "comments" in a program also "slow down" the compiling process because there is more "data" to read initially. Does that mean we should remove them ?