public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Terry Flannery" <terry.flannery@btinternet.com>
To: "Jeffrey C Knupp" <jknupp@andrew.cmu.edu>, <gcc-help@gcc.gnu.org>
Subject: Re: cpp
Date: Mon, 12 Aug 2002 11:37:00 -0000	[thread overview]
Message-ID: <000b01c2422f$4abe5940$c700a8c0@sknet01> (raw)
In-Reply-To: <Pine.GSO.4.44L-027.0208121409140.10598-100000@unix4.andrew.cmu.edu>

Have a look at the -Wundef flag

Terry

----- Original Message -----
From: "Jeffrey C Knupp" <jknupp@andrew.cmu.edu>
To: <gcc-help@gcc.gnu.org>
Sent: Monday, August 12, 2002 7:13 PM
Subject: cpp


> To whoever sees this,
> I'm a student at Carnegie Mellon University and I've been using the
> preprocessor, cpp, from gcc-3.1. I was wondering if and why when a
previously undefined
> identifier in an #if is used, there is no warning given. For example, if
> the first line of my program is "#if Y" and Y has not been defined, it
> will not execute the code (obviously), but it also won't tell me that the
> identifier wasn't defined. I was wondering if this was done for a reason.
> Hopefully, someone can give me an answer.
>
> Thanks,
> Jeff Knupp
> Carnegie Mellon University
>

      reply	other threads:[~2002-08-12 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-12 11:13 cpp Jeffrey C Knupp
2002-08-12 11:37 ` Terry Flannery [this message]

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='000b01c2422f$4abe5940$c700a8c0@sknet01' \
    --to=terry.flannery@btinternet.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jknupp@andrew.cmu.edu \
    /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).