public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@cygnus.com>
To: Peter Seebach <seebs@monolith.solon.com>
Cc: egcs@cygnus.com
Subject: Re: linux libio status
Date: Wed, 15 Oct 1997 22:29:00 -0000	[thread overview]
Message-ID: <u9oh4q46ox.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <199710160316.WAA21814@monolith.solon.com>

>>>>> Peter Seebach <seebs@monolith.solon.com> writes:

> In message < u9zpoarh0w.fsf@yorick.cygnus.com >, Jason Merrill writes:

>> This is why we have a NULL macro.  The gcc stddef.h provides an appropriate
>> definition, so we can put

>> #undef NULL
>> #define __need_NULL
>> #include <stddef.h>
>> #undef __need_NULL

>> somewhere strategic, and that should do the trick.

> Well, strictly speaking, I don't think that's correct - I *believe* a
> user who has not included <stddef.h> is allowed to assume that not everything
> in it is defined.

That's why we define __need_NULL.  That tells the gcc stddef.h that we only
want the definition of NULL, and nothing else.

Jason

  reply	other threads:[~1997-10-15 22:29 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-14 23:23 Joe Buck
1997-10-15  0:06 ` Richard Henderson
1997-10-15  0:52 ` Olivier Galibert
1997-10-15  8:25   ` [ECGS] " chip
1997-10-15 11:12   ` Joe Buck
1997-10-15 12:10     ` Olivier Galibert
1997-10-15 16:51       ` [ECGS] " chip
1997-10-15 20:16       ` Joe Buck
1997-10-15 20:16         ` Olivier Galibert
1997-10-16 12:53           ` Pal Engstad
1997-10-15 11:12   ` Peter Seebach
1997-10-15 20:16     ` Joe Buck
     [not found]   ` <199710151419.JAA20162.cygnus.egcs@monolith.solon.com>
1997-10-15 16:51     ` Jason Merrill
1997-10-15 20:16       ` Peter Seebach
1997-10-15 22:29         ` Jason Merrill [this message]
1997-10-16  8:31           ` Peter Seebach
1997-10-16 15:19             ` Jason Merrill
1997-10-16 12:53               ` Peter Seebach
1997-10-16 15:19       ` Paul Koning
     [not found] <199710150623.XAA06491.cygnus.egcs@atrus.synopsys.com>
1997-10-15  2:10 ` Jason Merrill
1997-10-15  9:15   ` Joe Buck
1997-10-15 11:12     ` Per Bothner
1997-10-15 14:33       ` Joe Buck
1997-10-15 16:51         ` Per Bothner
     [not found]         ` <199710152351.QAA02138.cygnus.egcs@cygnus.com>
1997-10-16  1:51           ` Jason Merrill
1997-10-16 12:58             ` Joe Buck
1997-10-17 12:53               ` Jason Merrill
1997-10-16 12:58             ` Alexandre Oliva
1997-10-15 16:51       ` Peter Seebach
1997-10-15 14:33     ` Richard Henderson
1997-10-15 12:10 Greg Galloway
1997-10-16 12:53 ` H.J. Lu
1997-10-15 12:10 Greg Galloway
1997-10-15 20:16 ` Joe Buck
1997-10-16 12:58 ` H.J. Lu

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=u9oh4q46ox.fsf@yorick.cygnus.com \
    --to=jason@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=seebs@monolith.solon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).