linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: C programming list <linux-c-programming@vger.kernel.org>
Subject: why no preprocessor #warning or #note directives?
Date: Sun, 22 Jan 2006 08:39:08 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0601220835530.4077@localhost.localdomain> (raw)


  not a big deal, but i'm curious why C hasn't been extended to
include the gcc extension #warning macro?

  more to the point, why not additional directives like, say, #note or
#info.  there are times (in gcc) when i want some feedback from the
preprocessor as it's running and i'll use #warning.  but i'm not happy
with that since what's happening isn't something that really requires
a "warning", it's just something i wanted to know about.

  was there ever any discussion to add an extra information directive
or two to the preprocessor?  just curious.  it doesn't seem like this
would be a major issue in terms of enhancement.

rday

                 reply	other threads:[~2006-01-22 13:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.63.0601220835530.4077@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).