… compat breakage and I can just make the change without bumping soversion or such, since I reduce the expectations on the type, not increase it. But what if this C API is used by C++ apps? i.e. enclosed in "extern "C"" kind of stuff?
-
-
Prikaži ovu nit
-
I know that C++ mangles "const" decorators and such into their symbol names, so adding it in C++ code would be compat borkage I guess. But do C++ compilers care if I change this in C prototypes? Tell me, Internet!
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
It certainly is not an ABI break, which is good. I'm not sure if it breaks pointers to that function on the API level, but it certainly does not break ABI, as long as it's C or extern C.
-
Ah, the pointers to functions thing is a good one. That indeed does mean this is an API break, because the ptrs to functions would stop being compatible. Thanks for the pointer (haha!), this resolves the question: yes, adding the "const" *is* an API break, though not ABI break.
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.