Project Organization in C Best Practices

Question

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?

score 3 · Accepted Answer · edited May 23 '17 at 12:32

3

You may be interested in answers to this question.

edited May 23 '17 at 12:32

Community

1
1

answered Apr 12 '09 at 20:44

mouviciel

66,855
13
106
140

score 1 · Answer 2 · answered Apr 12 '09 at 20:45

1

I think the best thing to do in your situation is just make sure your whole team is on the same page. This point can't be stressed enough. Have a standardized method of doing things and make sure your doing it.

answered Apr 12 '09 at 20:45

Kredns

36,461
52
152
203

score -2 · Answer 3 · answered Apr 12 '09 at 20:44

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.

Project Organization in C Best Practices

3 Answers3

Linked