mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Timur Tabi <ttabi@interactivesi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18 asm-alpha/system.h has a problem
Date: Mon, 18 Dec 2000 12:15:00 -0600	[thread overview]
Message-ID: <20001218184531Z132357-439+4699@vger.kernel.org> (raw)
In-Reply-To: <14910.10020.692884.302587@wire.cadcamlab.org>
In-Reply-To: <20001217153444N.dyky@df-usa.com> <20001218033154.F3199@cadcamlab.org>  <20001218154907.A16749@athlon.random>

** Reply to message from Peter Samuelson <peter@cadcamlab.org> on Mon, 18 Dec
2000 09:03:00 -0600 (CST)


> Not a compiler bug, a source bug of assuming a C header file can be
> included by a C++ program.  The right solution, as always, is to make a
> copy of the header (assuming you really do need it) and edit the copy
> as necessary. 

That just creates more maintenance problems.  What if the kernel header file
changes?  Then he'll have to change his copy as well.  He'll forever need to
check changes in that kernel header file, or risk having an obscure bug that's
otherwise hard to track.


Yes, it's perfectly valid C, but so what?  That doesn't mean that it's a good
idea.  It does no harm to make a minor change to the header file to allow a C++
compiler to digest it.  I consider it to be a "professional courtesy" of a C
programmer for a C++ programmer.  All the C programmer needs to do is
acknowledge that someone might want to use a C++ compiler on the code, and just
make a few minor changes that have no negative affect at all.


-- 
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com

When replying to a mailing-list message, please direct the reply to the mailing list only.  Don't send another copy to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-18 18:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-17 23:34 Daiki Matsuda
2000-12-18  9:31 ` Peter Samuelson
2000-12-18 14:49   ` Andrea Arcangeli
2000-12-18 15:03     ` Peter Samuelson
2000-12-18 15:14       ` Andrea Arcangeli
2000-12-18 15:24         ` Peter Samuelson
2000-12-18 15:41           ` Andrea Arcangeli
2000-12-18 18:15     ` Timur Tabi [this message]
2000-12-18 18:20       ` Miquel van Smoorenburg
2000-12-18 18:20       ` Alan Cox

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=20001218184531Z132357-439+4699@vger.kernel.org \
    --to=ttabi@interactivesi.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®