linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: pdovera <pdovera@bmind.it>
To: C-16 <pmr17184@students.fct.unl.pt>, linux-c-programming@vger.kernel.org
Subject: Re: #include problem
Date: Fri, 15 Oct 2004 19:04:29 +0200	[thread overview]
Message-ID: <4170031D.4010309@bmind.it> (raw)
In-Reply-To: <200410151648.i9FGmlqM026477@students.fct.unl.pt>

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.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>
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 ...

Ciao,
Paolo Dovera



  parent reply	other threads:[~2004-10-15 17:04 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 [this message]
2004-10-15 17:12   ` Eric Bambach
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=4170031D.4010309@bmind.it \
    --to=pdovera@bmind.it \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=pmr17184@students.fct.unl.pt \
    /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).