From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: fnasser@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/cli] s/NO_FUNCTION/NULL/
Date: Tue, 29 Jan 2002 02:10:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020129120916.6458G-100000@is> (raw)
In-Reply-To: <3C56237F.4090803@cygnus.com>
On Mon, 28 Jan 2002, Andrew Cagney wrote:
> In C, NULL is typically ``(void*)0''. What ever it is, it must be
> compatible with both data and code pointers.
>
> I think this makes using NULL more robust than NO_FUNCTION?
NULL _should_ be more robust than NO_FUNCTION, but you can never know
what GCC will invent next ;-)
I guess we can postpone this, and use NULL, until we see some
warnings. With any luck, that will never happen.
next prev parent reply other threads:[~2002-01-29 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 8:15 Andrew Cagney
2002-01-20 15:17 ` Andrew Cagney
2002-01-21 1:51 ` Eli Zaretskii
2002-01-21 8:51 ` Fernando Nasser
2002-01-21 9:19 ` Eli Zaretskii
2002-01-21 10:37 ` Andrew Cagney
2002-01-22 0:57 ` Eli Zaretskii
2002-01-28 20:51 ` Andrew Cagney
2002-01-29 2:10 ` Eli Zaretskii [this message]
2002-01-31 21:49 ` Andrew Cagney
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.SUN.3.91.1020129120916.6458G-100000@is \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.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