Message-ID: <37039AB0.85BF34FD@geocities.com> From: BartMan X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en,pl MIME-Version: 1.0 Newsgroups: comp.os.msdos.djgpp Subject: Re: A problem with debugging under Rhide, more data References: Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Lines: 26 Date: Thu, 01 Apr 1999 16:23:41 GMT NNTP-Posting-Host: 195.116.242.5 X-Complaints-To: abuse AT tpsa DOT pl X-Trace: news.tpnet.pl 922983821 195.116.242.5 (Thu, 01 Apr 1999 18:23:41 MET DST) NNTP-Posting-Date: Thu, 01 Apr 1999 18:23:41 MET DST Organization: TPNET - http://www.tpnet.pl To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote: > Do you use the #include directive to include the code of `VM_GetBack'? > If so, this is a known problem; see section 12.8 of the FAQ for > explanation and some solutions. Hans-Bernhard Broeker wrote: > You should never have nor want to #include a .cc file into another. > That's your part of the responsibility for that problem, > originally. If your program has more than one .cc file, compile each > of them to its own .o file, and link them together. #include is for > header files, and *only* for them. That's why Eli spoke about inline > functions: only they (as they will be in the header file) should > normally be #included in another .cc file. That's right! I've found, that I made a mistake. Since I'm self-learning C I didn't know that I can't include .c file to main file. My first contact with C was with Borland C and wasn't using a project files. First time I've met projects in Rhide, but old habbit stayed and I've #included .cc into main .cc project file. Now I know that I shouldn't do that, but I didn't know that before. Thank You Eli and Hans for help. Thanx! Bartek