From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] C++ compatible include files
Date: Tue, 22 Aug 2000 18:38:54 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205377@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205375@msgid-missing>
>>>>> On Tue, 22 Aug 2000 11:34:15 -0700 (PDT), David Mosberger <davidm@hpl.hp.com> said:
>>>>> On Tue, 22 Aug 2000 14:23:53 -0400, roneng@ca.ibm.com said:
Ronen> I was wondering if there are plans to make the ia64 kernel
Ronen> include files C++ compatible. In particular the ::: in the
Ronen> embedded assembly in system.h and atomic.h seems to prevent
Ronen> these files, and the files that include them (e.g. fs.h) from
Ronen> being included in C++ programs.
David> Umh, why are you including kernel headers? That's a
David> no-can-do, as Linus has stated repeatedly.
In case that isn't obvious: I was talking about including kernel
headers in _applications_. I'm assuming that's what you were trying
to do. If not, please explain.
--david
next prev parent reply other threads:[~2000-08-22 18:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-22 18:23 [Linux-ia64] C++ compatible include files roneng
2000-08-22 18:34 ` David Mosberger
2000-08-22 18:38 ` David Mosberger [this message]
2000-08-22 19:37 ` Jes Sorensen
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=marc-linux-ia64-105590678205377@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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