[RFC] Moving apart SGI extensions

[Gabriel Dos Reis]

Benjamin Kosnik <bkoz@redhat.com> writes:

| >     http://gcc.gnu.org/ml/libstdc++/2001-09/msg00158.html
| 
| Huh. Interesting.
| 
| 1) kludges: should be removed. I've been trying to remove them as I touch 
| the code, and I know you did a bunch of this already as well. I think 
| this is important.
| 
| 2) extensions. My preference is to not have a macro at all, and just move 
| individual bits to include/ext/some_name.h. Furthermore, it would be 
| great if the include/ext stuff was not in namespace std::, as it is presently 
| (gag!). I think this is a better idea then macros... besides, stuff in 
| /include/ext wouldn't have to be mangled, right? Since it's only brought 
| in by request and not part of the standard library proper? 

I agree with much you say.  Except that sometimes some extensions have
to be implemented as member functions or such (e.g. fd()-extention, or
C99 numeric functions which are part of <math.h>).
For those, one has to guard them with macros.

| It would be nice if /include/ext was 
| 1) in namespace __gnu_cxx
| 2) not mangled


Agreed.

-- Gaby
CodeSourcery, LLC                       http://www.codesourcery.com