![]() ![]() This is a constant work-in-progress issues and pull-requests are very welcome. So, I'm certain I'm wrong on even more points. I've changed my opinion multiple times on many of the rules in this document. Writing this guide has made me deeply consider, and reconsider, best C programming practices. These rules aren't intended to be universal admonitions about quality: they're just my preferences, and work well for what I do, and what I care about. Pick and choose what you like, and what works for your own situation. If you don't agree with something here, that's perfectly fine. I think we should use new technologies and new techniques if we can, to move everyone forward, if only a bit. In my opinion, backwards compatibility holds everyone back. Simplicity can often lead you to the best solution anyway: it's easier to write a linked list than it is to get an array to grow, but it's harder to index a list than it is to index an array.Ä«ackwards compatibility (e.g. ![]() Also, modern compilers will change computational complexities. Write correct, readable, simple and maintainable software, and tune it when you're done, with benchmarks to identify the choke points. I prioritize correctness, readability, simplicity and maintainability over speed because premature optimization is the root of all evil. I follow a few rules religiously, and others I use as a guideline. ![]() Some rules are as trivial as style, while others are more intricate. These are my favorite C programming practices. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |