30 Jun
2005
30 Jun
'05
4:31 p.m.
On Thu, 2005-06-30 at 08:30 -0400, David Abrahams wrote:
Dave Steffen
writes: I claim that our macros and use thereof is A) correct and B) safe. It just so happens that these macro constructs occasionally expand to something that has an extra semicolon, which triggers a warning in GCC 3.4 that we haven't seen before.
The warning will be an error on other compilers. The semicolons aren't just "bad style;" they're illegal.
I believe The Book specifically allows an optional semicolon at the end of a function declaration in the global scope. They are illegal in a class. And necessary at the end of a class/struct definition. I have a friend who runs into this problem a lot. :D Gen