Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <kettenis@jive.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [commit] Properly cast sentinels for concat()
Date: Tue, 05 Jul 2005 20:03:00 -0000	[thread overview]
Message-ID: <u3bqtotjs.fsf@gnu.org> (raw)
In-Reply-To: <200507050728.j657SueI005195@jop31.nfra.nl> (message from Mark Kettenis on Tue, 5 Jul 2005 09:28:56 +0200)

> Date: Tue, 5 Jul 2005 09:28:56 +0200
> From: Mark Kettenis <kettenis@jive.nl>
> CC: gdb-patches@sourceware.org
> 
>    But in Mark's case, NULL is defined as (void *)0, so it's a pointer,
>    not an int.
> 
> No it isn't, OpenBSD has
> 
> #define NULL	0L

Sorry, I got confused: you did mention `void *', but that was about
the GCC version of stddef.h.

> Not that I think that it is a good thing, but Andrew has been talking
> about making GDB compilable with a C++ compiler before.

I never understood why we should waste any efforts on that.

> Do you still want me to revert the patch?

Well, let's say that I dislike those casts very much.  So if there's
any reasonable chance to get the maintainers of OpenBSD and the
OpenBSD GCC port to fix this problem in the forseeble future, I'd
suggest to revert it.  If not, I'll yield.


  reply	other threads:[~2005-07-05 20:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 13:36 Mark Kettenis
2005-07-04 22:08 ` Eli Zaretskii
2005-07-04 23:16   ` Andreas Schwab
2005-07-05  1:32   ` Daniel Jacobowitz
2005-07-05  3:34     ` Eli Zaretskii
2005-07-05  4:23       ` Daniel Jacobowitz
2005-07-05  7:30       ` Mark Kettenis
2005-07-05 20:03         ` Eli Zaretskii [this message]
2005-07-05  7:36   ` Mark Kettenis

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=u3bqtotjs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=kettenis@jive.nl \
    /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