|
|
|
|
|
by pjc50
2297 days ago
|
|
There is an old but great book called "C traps and Pitfalls" on that subject. Otherwise you're left alone with yourself and your tooling. Things like valgrind help a lot. But I'll admit that I too find large C projects alarming; it may be better to write "C with classes" code in a C++ environment, so at least you have classes and namespaces as an organisational tool. |
|