Re: [boost] Macros at namespace scope: trailing semicolon?

From: Lucas Galfaso (lgalfaso_at_[hidden])
Date: 2005-07-14 20:37:29

Hi
"David Abrahams" <dave_at_[hidden]> wrote in message
news:ueka1s3zt.fsf_at_boost-consulting.com...
>
> I am defining a macro,
>
>  BOOST_PARAMETER_KEYWORD(tag_namespace, name)
>
> that declares a keyword for the Parameter library.  It has to be used
> at namespace scope.  I have the option to define it so that correct
> usage requires a trailing semicolon, or so that the trailing semicolon
> is forbidden.  Unfortunately I don't have the ability to make it
> optional.  Which should I choose?

The normal use for marcros do not requiere you to place an extra semicolon.
Macros are not function calls and should be treated different. The fact that
some people do not like macros and they think they polute the code, they
have two choices, you can embrase the use of macros, or just live with them
as macros are not going to be removed from the standard.

\TM

>
> IMO there's no chance of confusing it with a function call, since a
> function call would be illegal in the context in which it's used, and
> people are naturally more likely to add a semicolon without thinking
> about it, and if I design the macro so that a semicolon is required it
> will interact more smoothly with editors and pretty-printers.  So I
> can't see any good reason not to require the semicolon.  Arguments?
>
> -- 
> Dave Abrahams
> Boost Consulting
> www.boost-consulting.com
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>