   slicing the code
  I have a project that have about 4500 lines of code and most of the code is in one c file. it became a torture for me to compile it. even I change a line it takes so much time to compile the file for my celeron 500. does seperating the classes into different files help me gain some time? what should I care when seperating the files effectively? 
  If you split your file up un to smaller c files, the compiler only needs to re-compile the files that have edited.Try to use smaller files with some sensible functional grouping. Avoid including headers in other headers, if you can.   [edited by - willm on February 5, 2004 5:55:45 AM];  If you have functions that operate on a certain data structure then group them together into their own .c file. It will reflect the design abstraction. ''This .c file is for manipulating data of this type'' ;  My article on organising code files might help you. Take a look at the link in my signature.   [ MSVC Fixes | STL Docs | SDL | Game AI | Sockets | C++ Faq Lite | Boost  Asking Questions | Organising code files | My stuff | Tiny XML | STLPort] 