Peter,

Yep...

Macros are fun for the programmer but not so much fun for the company. I don't allow macros in our code development.

It just makes things non-standardized. If programmers are uing macros, they prefer their own and we end up with many macros doing the same thing and add more maintenance time to advise everyone of our macro library. Forget it. Been there - done that.

The only time we use macros is when we do a one-time contract for a customer we'll never see again. And that's not the type of customer we work for. Its like the message I wrote a few weeks ago, simplicity requires much less management.

Macro can be fun - I worked on a project where we wrote an 8x300 assembler in Intel macros. I've also written a laser-scanning bar code reader entirely in a macro language. It may cure boredom for theprogrammer at the sacrifice of efficiency, but writing mcros has all the disadvantages as writing in C. It masks detail, corrupts attention, grows bugs, distorts the real-time einsteinian continuum. :)

-Jay C. Box