> Thanks, I was wrong about that.
>
> Then I think we should just bite the bullet and provide the new
> behaviour. If we do have an abi_tag on those types in the next release
> then we can preserve the old behaviour in the old ABI and use the
> C++11 semantics for the abi_tagged type, which will be
>> Also the old standard seems to require that ios_base::fixed |
>> ios_base::scientific (or any other combination) falls through to the
>> uppercase test; I was trying to use abi_tag for a solution as not only
>> would two versions of _S_format_float be necessary, but also num_get
>> due to the pr
