Is there any point of using C over C++ nowadays? (Other than for some embedded devices that don't support newer standards I guess)
I never liked the OOP approach C++ provides, but I would gladly use C11 for some of my pet projects.
next page btw.
>need more manga about coding
Arguably, the best use case for C is in libraries, or at least the C ABI. It's a pain to get C++ libraries to be used with other languages, but C libraries are pretty trivial for FFIs. Granted, you can use C++ to do this, but if you're gonna extern "C" everything, you might as well just write in C.
>>61016788
>if you're gonna extern "C" everything
Not everything, just the exposed functions.
I don't know why /g/ pretends that making C++ extensions is somehow extremely difficult. I've implemented plenty of CPython extensions in C++ and I've extended Java code with JNI/C++ for over a decade.
It's fucking trivial, and no, it didn't require wrapping half the code in extern "C". I truly believe that the reason people continue to spout that bullshit about "hurr durr broken ABI" is because some poster read that somewhere on a blog in 2005 and others on /g/ are repeating it because they don't really know C++ and need to justify their ignorance.
>>61016788
Look at the c2
>>61017127
It's not that it's difficult, but there are some gotchas. One of those gotchas is exceptions, which are basically undefined behavior outside of the context of a C++ program.
>>61017320
>there are some gotchas
Well, that's true for C++ in general though.