From: Fernando Nasser <fnasser@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa/cli] s/NO_FUNCTION/NULL/
Date: Mon, 21 Jan 2002 08:51:00 -0000 [thread overview]
Message-ID: <3C4C46E8.F48A93D7@redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020121114951.16755I-100000@is>
Eli Zaretskii wrote:
>
> On Sun, 20 Jan 2002, Andrew Cagney wrote:
>
> > Do you have any problems with the below?
> >
> > Andrew
> >
> > > Hello,
> > >
> > > The attached replaces the NO_FUNCTION macro with NULL. If you
> > > examine the code, function.cfunc() is only sometimes assigned the
> > > value NO_FUNCTION and no code actually tests for a value of
> > > NO_FUNCTION. Consequently, I can't see any point in having this
> > > macro.
>
> IMHO, someone should test this change with the latest versions of GCC,
> including their development line: they could have their own ideas when
> you are allowed to pass NULL, especially with all the warning options
> we use.
Besides, the NO_FUNCTION documents the meaning better than NULL
(although most people should guess). Maybe you can add a comment
somewhere nearby.
Any chance Eli's concerns become true and we get a warning because
NULL is not typed properly? Maybe you would need a cast (in which
case I would prefer the NO_FUNCTION def.
Regards,
Fernando
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2002-01-21 16:51 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 [this message]
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
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=3C4C46E8.F48A93D7@redhat.com \
--to=fnasser@redhat.com \
--cc=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--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