From: Eljay Love-Jensen <eljay@adobe.com>
To: suresh@comodogroup.com, gcc-help@gcc.gnu.org
Subject: Re: Link problems in g++ but not in gcc!!
Date: Tue, 31 Aug 2004 20:35:00 -0000 [thread overview]
Message-ID: <6.1.2.0.2.20040831071219.0429e008@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <6.1.2.0.2.20040831070257.01f81858@iplan-mn.corp.adobe.com>
Hi L.Suresh,
CAVEAT!
If you make an "ipq.hpp" header file that only contains this...
extern "C" {
#include "ipq.h"
}
...that's just fine if ipq.h does not, itself, include any header files.
But if it does include any header files, your ipq.hpp should include those
header files first. And you should use the same guard that ipq.h uses --
but don't DEFINE it, just trigger off of it.
#ifndef ipq_h_once
#include "alpha.h"
#include <stdio.h>
extern "C" {
#include "ipq.h"
}
#endif
You don't want to compromise those other header files by extern "C"-ing them.
If the made-up "alpha.h" is, itself, in the same boat, then do this...
#ifndef ipq_h_once
#include "alpha.hpp" // "C" wrapper around alpha.h
#include <stdio.h>
extern "C" {
#include "ipq.h"
}
#endif
It can turn into a mighty be can-o'-worms if there are lots and lots of
header files. Might be easier to instrument (edit) the C header files with
the...
#ifdef __cplusplus
extern "C" {
#endif
HTH,
--Eljay
prev parent reply other threads:[~2004-08-31 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 12:09 L.Suresh
2004-08-31 12:18 ` Eljay Love-Jensen
2004-08-31 20:35 ` Eljay Love-Jensen [this message]
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=6.1.2.0.2.20040831071219.0429e008@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=suresh@comodogroup.com \
/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).