[PATCH] For SGI stl_algo.h extensions (was: Re: [RFC] Moving apart SGI extensions)

[Gabriel Dos Reis]

Paolo Carlini <pcarlini@unitus.it> writes:

| Gabriel Dos Reis wrote:
| 
| > | Right: algorithm is ok. #include <ext/algorithm> is nice! I'm correcting this.
| > | For the include guard I propose _EXT_ALGORITHM, however. What do you think?
| >
| > I don't think that is necessary: By the point the user says
| > #include <ext/algorithm>, he is already asking for nonstandard
| > features and I don't think we should go another macro step further in
| > order to have the requested functionnalities in.
| 
| I'm wondering if perhaps there is a misunderstanding here.

My apologies then

| By "include guards" I meant (perhaps it is not good English, sorry about that) the
| *global* include guards, which are commonly used to avoid a double inclusion of a whole
| file, *not* a preprocessor directive which enables a specific feature on request (as we
| currrently do with _GLIBCPP_RESOLVE_LIB_DEFECTS, for instance)
| 
| Ok?

Yes!

Thanks,

-- Gaby