LegibleCrimson2

4 ms·

1. 1.▲
   by LegibleCrimson2 2y ago

   As long as I can't silently get wrong behavior or runtime crashes, I'm happy enough. Is it guaranteed that an incorrect calling convention will always cause a compiler error? I wasn't aware the calling convention was consider
2. 2.▲
   by LegibleCrimson2 2y ago

   Ah, yeah, you're right. I was spacing the fact that C as well as C++ can have multiple calling convention. I blame early morning brain. As far as the wrong calling convention goes, I'm basing it on the fact that an extern "C+
3. 3.▲
   by LegibleCrimson2 2y ago

   A couple big caveats here: * cdecl is a platform specific calling convention. There is no standard C ABI. cdecl is a wintel thing, not the standard C calling convention. On Linux, this is the System V ABI for instance. On Windows ARM, it&#x
4. 4.▲
   by LegibleCrimson2 2y ago

   > `extern "C"` has nothing to do with linkage, all it does is disable namemangling, so you get the same symbol name as with a C compiler. extern "C" also ensures that the C calling convention is used, which is relevan