linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "C-16 " <pmr17184@students.fct.unl.pt>
To: linux-c-programming@vger.kernel.org
Subject: Re: #include problem
Date: Fri, 15 Oct 2004 18:29:56 +0100	[thread overview]
Message-ID: <200410151729.i9FHTu0h027788@students.fct.unl.pt> (raw)

> On Friday 15 October 2004 11:48 am, 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
> 
> You want to use whats called header guards.
> 
> -----------------aaa.h----------
> 
> #ifndef AAA_H
> #define AAA_H
> 
> #include "xxx.h"
> 
> ...some code
> 
> #endif
> ----------------end aaa.h---------
> ----------------xxx.h--------------
> 
> #ifndef XXX_H
> #define XXX_H
> 
> .....some code
> 
> #endif
> ----------------end xxx.h----------
> 
> Notice that the endif must be the very last line of the file or you
defeat the 
> whole purpose of header guards. Others may or may not actually call them 
> header guards, but thats the phrase I was taught. Its good practice to 
> *always* use these in your header files. It solves many simple double 
> inclusion and inclusion loop problems.
> 
> ----------------------------------------
> 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 
> 
It worked !! :) thanks a lot

"Exploration is knowledge"

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-15 17:29 C-16  [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-15 16:55 #include problem Huber, George K RDECOM CERDEC STCD SRI
2004-10-15 16:48 C-16 
2004-10-15 17:04 ` Eric Bambach
2004-10-15 17:04 ` pdovera
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

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=200410151729.i9FHTu0h027788@students.fct.unl.pt \
    --to=pmr17184@students.fct.unl.pt \
    --cc=linux-c-programming@vger.kernel.org \
    /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).