Re: throw(), pure and const flags on functions

[Paolo Carlini <paolo dot carlini at oracle dot com>]

Hi,
> I'd go so far as to suggest __GLIBCXX_PURE, but that's of course a call
> for the libstdc++ maintainers to make.  I'd try to use as small a chunk
> of the macro namespace as possible...  Do macros get expanded inside
> attributes?  If so, can we use "__attribute__ ((__pure__))" instead of
> "pure"?
>   
Mark, first thanks for your advice, two days ago, I'm trying to adhere
to it ;)

Indeed, I think the macro should use __pure__ in the C++ library. As for
the name, we are in fact consistently prepending _GLIBCXX_ (single
underscore at the beginning). Honza can find many examples in c++config.

Paolo.