title: C theory/general practice related to "splitting" the system into x number of source files
body: <p>I have a quick question when programming in C. I am writing a simple application in C as the title suggests but i find myself defining rather large functions in separate source files so it makes maintenance and debugging much easier but my question is is there a standard X amount of lines in a c source file before you should "split" it up into multiple files or is it very dependant on the system/functions in question.</p>
  
  <p>Say for example i have 20 source files with 1 function in each say the functions are somewhat related but they all do different things (e.g. they all manipulate the same struct in some way) should you in theory have these 20 files, or 1 larger file with 20 functions and keep the modification of X structure in the same file?</p>
  
  <p>My idea is the more "split" the better/easier the coding becomes, but then again im quite new to C.</p>
  
  <p>Any input will be appreciated.</p>
  
  <p>Cheers,
  Chris.</p>