Date: Thu, 14 Nov 2024 14:44:50 +0100
On 2024-11-14 at 12:42, Frederick Virchanza Gotham via Std-Proposals wrote:
> I think the committee should consider giving Microsoft a certain
> amount of time to change this. I realise that the Standard doesn't
> mention 'Microsoft' in its text but the committee could make the
> decision that in C++36, the above two points are possible (which would
> mean that MS have to change their ABI by then).
The standard contains the rules that compiler manufacturers can agree
upon. If you add rules they don't like, or cannot implement because
their other customers don't want it, they will just be "almost
compliant" with the next release.
For example, the C++ standard removed trigraphs which was "only" used by
IBM customers using EBCDIC encoding. So this is now a "language
extension", still available in IBM's compilers.
> I think the committee should consider giving Microsoft a certain
> amount of time to change this. I realise that the Standard doesn't
> mention 'Microsoft' in its text but the committee could make the
> decision that in C++36, the above two points are possible (which would
> mean that MS have to change their ABI by then).
The standard contains the rules that compiler manufacturers can agree
upon. If you add rules they don't like, or cannot implement because
their other customers don't want it, they will just be "almost
compliant" with the next release.
For example, the C++ standard removed trigraphs which was "only" used by
IBM customers using EBCDIC encoding. So this is now a "language
extension", still available in IBM's compilers.
Received on 2024-11-14 13:44:51