Reputation: 2696
I am wondering what the best practices are for organizing a large C project are. It is a professional project, not an open source one, likely to be stored in a Git repository. How should things be sorted? Where should structures go? When should one use functions attached to structures versus functions that take a structure as a parameter?
In terms of laying out the files in the project, how should things come together? What naming conventions are most appropriate?
Upvotes: 6
Views: 12851
Reputation: 452
For large projects, my personal method is that everything gets its own folder. i.e.:
Root --> (Classes, Structs)
Classes --> (ClassA, ClassB)
Structs --> (StructA, StructB)
If needed, you can further split up a StructA or Struct B...
StructA --> (Methods,Struct)
etc.
Upvotes: -2