Development status

[Gabriel Dos Reis]

Jason Merrill <jason@cygnus.com> writes:

| >>>>> Nathan Myers <ncm@cantrip.org> writes:
| 
|  >> Use of -fnew-abi is strongly discouraged, it is an experimental
|  >> feature and subject to change without notice. I don't see why that is
|  >> required for gcc 2.95.2; if -fsquangling is what you really want, then
|  >> use that.
| 
|  > Hey, libstdc++-v3 is an experimental library.  We have to get the
|  > new ABI nailed down, and gcc-3 will probably be our last chance to
|  > do it.  We had better work out any problems now, and freeze the ABI 
|  > as soon as possible.  The only way that can happen is if people 
|  > using snapshots of libstdc++-v3 routinely use -fnew-abi.  That's OK, 
|  > because they don't expect binary compatibility between versions
|  > anyway.
| 
| -fnew-abi is under active development at the moment, and regularly changes
| from day to day.  And probably doesn't work most of the time.  

As does the whole CVS tree.

| ... Better to
| wait for it to stabilize...

I understand this might be a reasonable position.  But I also think
that the wider the new ABI stuff gets tested, the bigger are our
chance to spot bugs.  And v3 is a place where we can start that sort
of test.

-- Gaby