public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Aaron Case" <aaron.case@dynazign.com>
To: <gcc-help@gcc.gnu.org>
Subject: multiple inclusion of header files accross
Date: Mon, 15 Sep 2003 19:11:00 -0000	[thread overview]
Message-ID: <GBEOKKOEOGFDMKDFCHIMAEGBCAAA.aaron.case@dynazign.com> (raw)

Hello,

Is there a ld switch to address the problem of multiple inclusion of header
files accross object files.  I have used #ifndef and #define to prevent
multiple inclusion within an object file successfully.

Or should this be address in the makefile?  The current structure of the
makefile compiles several objects and then links the objects together but,
but some header files are included in almost all the source files used to
make each object.

Or should this be addressed by reorganizing my header files and throwing in
a few extern keywords?

Thanks in advance?

Aaron Case

             reply	other threads:[~2003-09-15 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 19:11 Aaron Case [this message]
2003-09-15 19:49 ` Eljay Love-Jensen
2003-09-15 21:15 lrtaylor

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=GBEOKKOEOGFDMKDFCHIMAEGBCAAA.aaron.case@dynazign.com \
    --to=aaron.case@dynazign.com \
    --cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).