public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: Rob Prowel <tempest766@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: please remove reserved word "new" from kernel headers
Date: Wed, 6 Jul 2005 14:58:34 +0200	[thread overview]
Message-ID: <9a874849050706055831ec5aae@mail.gmail.com> (raw)
In-Reply-To: <20050706092657.95280.qmail@web60012.mail.yahoo.com>

On 7/6/05, Rob Prowel <tempest766@yahoo.com> wrote:
> [1.] One line summary of the problem:
> 
> 2.4 and 2.6 kernel headers use c++ reserved word "new"
> as identifier in function prototypes.
> 
"new" is not a reserved word in C. the kernel is written in C.


> [2.] Full description of the problem/report:
> 
> When kernel headers are included in compilation of c++
> programs the compile fails because some header files
> use "new" in a way that is illegal for c++.

Userspace programs should not include kernel headers directly.

But, if you really want it changed I suggest you create a patch and
submit that for review/inclusion and see what feedback you get.


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  parent reply	other threads:[~2005-07-06 17:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06  9:26 PROBLEM: please remove reserved word "new" from kernel headers Rob Prowel
2005-07-06 12:56 ` Jurriaan on adsl-gate
2005-07-06 12:58 ` Jesper Juhl [this message]
2005-07-06 13:06 ` Alexey Dobriyan
2005-07-06 18:08   ` Richard B. Johnson
2005-07-06 13:14 ` David Woodhouse
2005-07-06 14:05 ` Jakob Oestergaard
2005-07-06 14:43 ` Michal Schmidt
2005-07-06 15:35 ` Schneelocke

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=9a874849050706055831ec5aae@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tempest766@yahoo.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