Thread: Separating out code into multiple files

Hi. I have a source file that's 1700 lines long. Attached to it is a header file that's only 25 lines long. The interface is designed to be as simple as possible, though the implementation of what goes on underneath the surface is quite complex.

1700 lines is getting a bit unmanageable. The code uses two internal data structures, each of which come with a set of functions designed to work on the data. I'd like to separate the structures and functions into their own source files.

Yet, those types will only be used by this original source file. For me to declare all the functions and structures in such a way that they can be accessed by all other translation units ruins my concept of keeping the interface as simple as possible and keeping data and functions as private as possible. So what do I do? Do I do this in the .c file:

Code:

#include "Morestuff.c"

TIA, Richard

First of all 1700 lines is not unheard of for C source files...

Your best bet is to break it out functionally... for example: User interface in one file, file access in another, networking in a third and so on.
Then for each file make a header with function prototypes and any extern variables and typedefs you need. The headers (.h) would then be included into your main, and other files as needed.