linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Bambach <eric@cisu.net>
To: pdovera <pdovera@bmind.it>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: #include problem
Date: Fri, 15 Oct 2004 12:12:04 -0500	[thread overview]
Message-ID: <200410151212.04356.eric@cisu.net> (raw)
In-Reply-To: <4170031D.4010309@bmind.it>

On Friday 15 October 2004 12:04 pm, you wrote:
> C-16 wrote:
> >Howdy,
> >i have a file main.c in my program that needs to include four headers
> >aaa.h , bbb.h ,ccc.h and ddd.h . Each one of these headers need to
> >include another header xxx.h . With this implementation i get a
> >"redefinition" compilation error. How can i solve this problem ? Thanks
> >in advance.
>>
> Hi,
> If I understand well the redefinition problem is generated by xxx.h, so
> you need to include xxx.h only once.
>
> into each file aaa.h, bbb.h, ccc.h, try the following code:
>
> #ifndef xxx_h
> #include "xxx.h"
> #endif
>
> so you will include xxx.h only once !
> xxx_h will not be included only the first time, the second time the
> ifndef will be false (since xxx.h is already included) and so on ...

	This approach assumes he defines xxx_h in xxx.h. From the description I dont 
think he does. Anyways, this approach is backwards and the #ifndef business 
shouldn't be in each header file that needs xxx.h but rather in xxx.h itself. 
There have been many great replies to his problem that illustrate this. 
Imagine if he had 60-70 .cc/.h files needing xxx.h...... its impractical to 
maintain and write the #ifndefs in each file instead of writing it once in 
the xxx.h file.

> Ciao,
> Paolo Dovera
>
-- 
----------------------------------------
EB

> All is fine except that I can reliably "oops" it simply by trying to read
> from /proc/apm (e.g. cat /proc/apm).
> oops output and ksymoops-2.3.4 output is attached.
> Is there anything else I can contribute?

The latitude and longtitude of the bios writers current position, and
a ballistic missile.

		--Alan Cox 2000-12-08 

----------------------------------------

  reply	other threads:[~2004-10-15 17:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-15 16:48 #include problem C-16 
2004-10-15 17:04 ` Eric Bambach
2004-10-15 17:04 ` pdovera
2004-10-15 17:12   ` Eric Bambach [this message]
2004-10-15 21:15 ` Jan-Benedict Glaw
2004-10-18  7:03 ` Ranga Makireddy
2004-11-07  3:39 ` Wayne Wu
  -- strict thread matches above, loose matches on Subject: below --
2004-10-15 16:55 Huber, George K RDECOM CERDEC STCD SRI
2004-10-15 17:29 C-16 

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200410151212.04356.eric@cisu.net \
    --to=eric@cisu.net \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=pdovera@bmind.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).