Timeline for Why does C provide language 'bindings' where C++ falls short?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5 at 21:14 | comment | added | John Dallman | People who have had to cope with a change of C++ ABI on the platform they were using tend to be adverse to doing it again. I've dealt with two (Sun C++ v4 to v5, and GCC 3,3 to 3,4) and will always recommend a C binding over a C++ one. | |
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| May 4, 2015 at 14:33 | comment | added | DeadMG | @Random832: Which is completely irrelevant when the C++ side can simply offer the C interface. You don't have to implement the binding in C to offer a C binding. | |
| May 4, 2015 at 13:34 | comment | added | Random832 | The other issue with providing a binding from a C++ library to another language is that the other language may require bindings to be implemented in C. Or, for languages that have something like (.NET) P/Invoke or (python) ctypes, it may not provide any tools for using the C++ ABI. | |
| May 4, 2015 at 12:58 | history | answered | Josh Kelley | CC BY-SA 3.0 |