From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: C++, Multiple Files, Classes Date: 6 Jan 2000 13:24:08 GMT Organization: Aachen University of Technology (RWTH) Lines: 17 Message-ID: <85251o$cpr$1@nets3.rz.RWTH-Aachen.DE> References: <3873FF7B DOT DFB48EA2 AT wt DOT net> <387460b5 AT news DOT uni-bielefeld DOT de> <38748E6B DOT 787F0BF6 AT wt DOT net> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 947165048 13115 137.226.32.75 (6 Jan 2000 13:24:08 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 6 Jan 2000 13:24:08 GMT User-Agent: tin/1.4-19991113 ("No Labels") (UNIX) (Linux/2.0.0 (i586)) Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Aaron Chernosky wrote: > I'm using DJGPP v2.02 with RHIDE v1.4... and it doens't compile... it > gives me those errors... so your saying I should do the includes > backwards? Include the cpp file in my main file and have the cpp include > the header? No. Don't #include the cpp file from any other file *at all*. Instead, make both your main source and the class .cpp file elements of your RHIDE project, and let RHIDE take care of how to compile each of them, separately, and then put the whole thing together in a final step. You'll want to learn about organizing sources into multiple files, from the ground up. The DJGPP FAQ has an article about that, if memory serves. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.