On Feb 24, 2008, at 9:50 PM, [EMAIL PROTECTED] wrote:
Curt -
1. Ok.. I see that I have cpptaskb4... which is what the download
section
had available... so checking it out of SVN now, and will try again.
2. In general, I've always adhered to the standard of always leaving
off
the last semicolon of the macro. This way I can treat the macro as a
statement and terminate it with a semicolon in the main body of the
code.
I started with this a long time ago (late 80's), at the time I
believe some
static checking tool would complain about empty statements also,
which is
why my employer at the time had a strict coding guideline about
macros.
I am not sure that I am qualified to definitely state whether one is
better
than the other, but I would say that (in my opinion) you should
change the
macro :-)
The macros were part of a scramble to address LOGCXX-219. I had to do
a couple of iterations since each version of VS added a new twist and
ran into a wall with VS9. I didn't have any compiler that warned me
of the double semis.
I'm about to crash and book tomorrow, but will commit something
tomorrow. I'd expect to roll a RC3 in 24-48 hours.
Does anyone know a gcc switch that will warn of the double semi's but
not that much more?
