From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb@sourceware.org, cagney@gnu.org, eliz@gnu.org
Subject: Re: A case for `void *' for pointers to arbitrary (byte) buffers
Date: Wed, 04 May 2005 14:45:00 -0000 [thread overview]
Message-ID: <200505041439.j44EddSb000734@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050503222744.GA10500@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 3 May 2005 18:27:44 -0400)
Date: Tue, 3 May 2005 18:27:44 -0400
From: Daniel Jacobowitz <drow@false.org>
To be honest, my preference is still for gdb_byte * over uint8_t *, for
exactly the reason Stan just mentioned: consistency. Whether that's
defined as unsigned char or uint8_t is less important to me.
So there seems to be a concensus for using `gdb_byte' for target byte
buffers. Unless Eli has anything to add to the discussion, I'll
consider this discussion closed.
Does gdb_byte, defined in terms of uint8_t, work for you?
This would be silly. It's not that `uint8_t' will be anything other
than `unsigned char' on any system supported by gdb in the foreseeable
future. Let's simply add
typedef unsigned char gdb_byte;
to "defs.h" and use that in any future changes. Andrew, you want to
do the honour?
Once that is done, people should update the targets they maintain to
use it and get rid of `bfd_byte' ASAP.
Mark
next prev parent reply other threads:[~2005-05-04 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42710E90.3030300@gnu.org>
[not found] ` <200504281919.j3SJJKF1011501@elgar.sibelius.xs4all.nl>
[not found] ` <42715EE8.5070704@gnu.org>
[not found] ` <01c54c8a$Blat.v2.4$ffbe8140@zahav.net.il>
[not found] ` <42753958.70109@gnu.org>
[not found] ` <01c54e92$Blat.v2.4$5cf24460@zahav.net.il>
[not found] ` <42755FD4.8000009@gnu.org>
[not found] ` <01c54f4a$Blat.v2.4$a9fc8500@zahav.net.il>
[not found] ` <42778DE6.1080106@gnu.org>
2005-05-03 20:17 ` Mark Kettenis
2005-05-03 20:23 ` Daniel Jacobowitz
2005-05-03 21:14 ` Mark Kettenis
2005-05-03 21:16 ` Daniel Jacobowitz
2005-05-03 22:10 ` Mark Kettenis
2005-05-03 22:28 ` Daniel Jacobowitz
2005-05-03 22:31 ` Joel Brobecker
2005-05-04 14:45 ` Mark Kettenis [this message]
2005-05-04 20:36 ` Eli Zaretskii
2005-05-04 15:40 ` Andrew Cagney
2005-05-04 17:57 ` Eli Zaretskii
2005-05-03 22:01 ` Stan Shebs
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=200505041439.j44EddSb000734@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
/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