3 ms·
I hear your pain. I'm trying to roll my pet project with C only (it suits me better, since I'm not a full time programmer). I'm using clang on OSX and gcc on li
by Keyframe 13y ago
I hear your pain. I'm trying to roll my pet project with C only (it suits me better, since I'm not a full time programmer). I'm using clang on OSX and gcc on linux and mingw on Windows (all x64, of course). There is something that bothers me though. I feel like I have made a grave mistake. Everything I look up that I need for my project there exists a suitable library for C++, but not for C. This surprised me. Maybe I don't know my way around libraries for C, but it seems like I have to reinvent wheel (badly so) if I want to stay with C. So now I'm thinking if I should just let go of C and do C with classes, which bothers me tremendously.
- yoklov 13y agoHeh, I'm familiar with that problem. I write in both C and C++ regularly, and be assured, the one I'm not using always seems better (maybe Google is just trolling me by showing me the results for the wrong language). I can only find C libraries or tools when I search for C++ libraries, and vice versa. If you're doing low level work (e.g. the layout of your objects is a concern to you), stick with C. C++ often gets in the way there and you won't be able to write idiomatic C++. If it's midlevel you're better off with C++. If it's high level, neither of these are a good fit, and you're better off looking elsewhere.
- Keyframe 13y agoIt would be nice if we had a central repository for C libraries, like old CPAN. I know they can't be universal, but repo could be. Github is sometimes nice to browse aroynd, but not really that great with discovering/searching stuff.