From: "Seyran Avanesyan" <seyran.avanesyan@tanner.com>
To: <gcc-help@gcc.gnu.org>
Subject: RE: extern "C" From command line
Date: Sat, 23 Aug 2008 02:46:00 -0000 [thread overview]
Message-ID: <D66102A43110FC488698F1C3B605E93108F962C2@exchange01.tanner.com> (raw)
In-Reply-To: <48AF7666.E16B03F1@dessent.net>
> Then you need C linkage, which means you have no choice but to enclose
> the code in "extern C" (or compile it with a C compiler of course.)
If
> you really can't modify the source.cpp file then I still don't see why
> you can't do something like:
>
> extern "C" {
> #include "source.cpp"
> }
Well, I can't do that because source.cpp allowed to contain #include-s.
(Of course I can parse source.cpp and create modified_source.cpp. Just
need to preprocess, then use yacc/lex or Spirit C-grammar parser...)
I can also write my own, simplified grammar parser for source.cpp (since
source.cpp is using C syntax).
But I just tried to compile with "-x c++" with extern "C" in souce.cpp
(experimentally added that manually), and when I tried to call it from
MSVC app I've got a crash.
next prev parent reply other threads:[~2008-08-23 2:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 16:12 Restricting symbol binding within shared object Arindam
2008-08-19 16:58 ` special comments handling in the C compiler Tim Wang
2008-08-22 1:52 ` extern "C" From command line Seyran Avanesyan
2008-08-22 2:12 ` Brian Dessent
2008-08-23 1:38 ` Seyran Avanesyan
2008-08-23 2:37 ` Brian Dessent
2008-08-23 2:46 ` Seyran Avanesyan [this message]
2008-08-22 2:04 ` 64-bit gcc Seyran Avanesyan
2008-08-22 11:01 ` Brian Dessent
2008-08-22 20:09 ` Seyran Avanesyan
2008-08-22 22:32 ` Brian Dessent
2008-08-22 22:45 ` Seyran Avanesyan
2008-08-23 2:31 ` Brian Dessent
2008-08-23 2:45 ` NightStrike
2008-08-23 2:49 ` Seyran Avanesyan
2008-08-23 3:18 ` Brian Dessent
2008-08-23 2:00 ` NightStrike
2008-08-23 2:13 ` Seyran Avanesyan
2008-08-19 18:49 ` Restricting symbol binding within shared object Ian Lance Taylor
2008-08-20 19:36 ` Arindam
2008-08-21 4:43 ` Ian Lance Taylor
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=D66102A43110FC488698F1C3B605E93108F962C2@exchange01.tanner.com \
--to=seyran.avanesyan@tanner.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).