Comparing C and C++ usage and performance with a real world project

Re:Comparing C and C++ usage and performance with a real wor... by overgard on Tuesday September 05, 2017 @09:49AM (#15175092)

> If you use the same compiler, ABI is a non-issue

And yet... microsoft releases a new compiler every two years or so, and not every library you use is going to update at the same time. This is a huge frustration for a lot of people.

I write c++ professionally and I've seen people waste weeks on these things, and most the libraries we wrote had plain c interfaces because being able to use other languages to call into the code was important and c++ is a nightmare with that.

[ Parent | on HN ]

Re:Comparing C and C++ usage and performance with a real wor... by aidenn0 on Tuesday September 05, 2017 @08:21PM (#15180179)

Yeah, MSVC breaking ABI is somewhat annoying, but I am also used to keeping the most recent half-dozen MSVC's installed.

VS 6.0 is getting very hard to source legally these days, and I wish MS made it easier to get.

As far as having high-level languages call directly into C++, yes that's quite a pain (nearly impossible without something like https://github.com/rpav/c2ffi). Note also that calling into non-C ABI functions in any language is hard (and most HLLs don't support anything like extern "C" to make it easy).

[ Parent | on HN ]