As I already told in the first line:
Including a cpp file is a bad programming practice.
But it happens, I have seen it many times.
Jaap
> -----Original Message-----
> From: Christian Sch=E4fer [mailto:ca...@kr...]
> Sent: Tuesday, May 20, 2003 10:34 AM
> To: dev...@li...
> Cc: dev...@li...
> Subject: Re[2]: [Dev-C++] Why would I want to #include a .cpp file?
>=20
>=20
> hi,
>=20
> Tuesday, May 20, 2003, 10:12:29 AM, you wrote:
> > 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,=20
> > you can split it in source1.cpp and source2.cpp of 500 lines, and=20
> > create source.cpp containing=20
> > #include "source1.cpp"=20
> > #include "source2.cpp"
>=20
> but why the hell would you do that?
> why don't you write a header file for class and/or (public) method
> declaration and include that then?
>=20
> the definitions can be split over as many files as you like only
> including the header file.
>=20
> =20
> gruss
> /Christian mailto:ca...@kr...
>=20
> ---
>=20
>=20
> I propose that the following character sequence for joke markers:
>=20
> :-)
>=20
> 19-Sep-82 11:44 Scott E Fahlman
>=20
>=20
>=20
> -------------------------------------------------------
> 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
>=20
|
