News for hackers. Stuff that matters.

A comment on The C++ Lifetime Profile: How It Plans to Make C++ Code Safer. Parent comment

Re:The C++ Lifetime Profile: How It Plans to Make C++ Code S... by zabzonk on Friday January 24, 2020 @11:39AM (#22139808)
> standard ABI, which C provides but C++ does not

Neither the C Language Standard nor the C++ Language Standard specify an ABI.

[ Parent | on HN ]
Re:The C++ Lifetime Profile: How It Plans to Make C++ Code S... by DoofusOfDeath on Friday January 24, 2020 @12:50PM (#22140655)
> Neither the C Language Standard nor the C++ Language Standard specify an ABI.

Perhaps we should distinguish between a Langage-Standard ABI vs. a per-platform de facto ABI.

I think the GP's comment holds for the latter definition.

[ Parent | on HN ]
Re:The C++ Lifetime Profile: How It Plans to Make C++ Code S... by zabzonk on Friday January 24, 2020 @01:10PM (#22140874)
I don't believe that either the GCC or MSVC C ABIs have been the same (per platform) over the years.
[ Parent | on HN ]
Re:The C++ Lifetime Profile: How It Plans to Make C++ Code S... by temac on Friday January 24, 2020 @02:51PM (#22141815)
For C: both platform have been EXTREMELY compatible over the years. They probably both treat breakage as bug. This is a must given the fundamental APIs are defined in term of C headers, and must remain compatible.

Even for C++: gcc has been mostly compatible, but not unreasonably so. MSVC was traditionally not at all, but has recently been for 2 or 3 major versions in a row. I think MSVC will eventually break it again though, but at least they break it way less often than before (and breaking can also have advantages).

[ Parent | on HN ]