RE: [Dev-C++] Why would I want to #include a .cpp file?

[Jaap de W. <wo...@ne...>]

Including a cpp file is a bad programming practice.
However, some guys do it when their source files become to big.
For instance when you have a source.cpp file of 1000 lines, 
you can split it in source1.cpp and source2.cpp of 500 lines, and 
create source.cpp containing 
#include "source1.cpp" 
#include "source2.cpp"

But you better put some more effort, and make it normal source files, 
which you can compile independend

Jaap


> -----Original Message-----
> From: Daniel Glenfield [mailto:sp...@ho...]
> Sent: Tuesday, May 20, 2003 9:57 AM
> To: dev...@li...
> Subject: [Dev-C++] Why would I want to #include a .cpp file?
> 
> 
> hi all,
> has anyone had to #include a .cpp file before? Under what 
> circumstances 
> would you need to do this? I know global variables can go in 
> headers so 
> that's not it, and function headers will do if you want a 
> function from a 
> .cpp file, so why would you need to do this?
> 
> Daniel
> 
> _________________________________________________________________
> Hotmail messages direct to your mobile phone 
> http://www.msn.co.uk/msnmobile
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>