Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: cagney@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Use bfd_byte in value.h
Date: Thu, 28 Apr 2005 19:19:00 -0000	[thread overview]
Message-ID: <200504281919.j3SJJKF1011501@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <42710E90.3030300@gnu.org> (message from Andrew Cagney on Thu, 28 Apr 2005 12:25:52 -0400)

   Date: Thu, 28 Apr 2005 12:25:52 -0400
   From: Andrew Cagney <cagney@gnu.org>

   This changes value.h to use bfd_byte more consistently.  When trying to 
   fix the signed (string) VS unsigned (buffer) pointer warnings you very 
   quickly run into these interfaces.

Hacking on a mac again?

Anyway, to place my previous comments about this issue in a context,
this really is analogous to strxxx() versus memxxx().  This gives a
clue to what the proper pointer type for these buffers is: `void *'.
I guess GDB's K&R history really shows here.  Does converting to `void
*' require more effort than simply replacing things with `bfd_byte *'?

Mark


  reply	other threads:[~2005-04-28 19:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 16:27 Andrew Cagney
2005-04-28 19:19 ` Mark Kettenis [this message]
2005-04-28 19:21   ` Daniel Jacobowitz
2005-04-28 22:12   ` Andrew Cagney
2005-04-29  7:15     ` Eli Zaretskii
2005-05-01 20:19       ` Andrew Cagney
2005-05-01 20:41         ` Mark Kettenis
2005-05-01 21:13         ` Eli Zaretskii
2005-05-01 23:04           ` Andrew Cagney
2005-05-02 19:12             ` Eli Zaretskii
2005-05-03 14:43               ` Andrew Cagney
2005-05-03 19:55                 ` Eli Zaretskii
2005-05-03 20:01             ` Daniel Jacobowitz

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=200504281919.j3SJJKF1011501@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=cagney@gnu.org \
    --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