From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org, cagney@gnu.org, eliz@gnu.org
Subject: Re: A case for `void *' for pointers to arbitrary (byte) buffers
Date: Tue, 03 May 2005 22:28:00 -0000 [thread overview]
Message-ID: <20050503222744.GA10500@nevyn.them.org> (raw)
In-Reply-To: <200505032206.j43M6QEN002791@elgar.sibelius.xs4all.nl>
On Wed, May 04, 2005 at 12:06:26AM +0200, Mark Kettenis wrote:
> > If you want to use a standard type, play the necessary autoconf games
> > to acquire stdint.h. Use uint8_t *.
> >
> > That's an interesting suggestion. It might take a few iterations to
> > get that right though.
>
> I'm willing to do the work.
>
> OK great! I really like being able to use those (u)intN_t types, and
> especially (u)intptr_t. You can probably steal the autoconf checks
> from GNU coreutils. Those will have been pretty well tested I sppose.
> But the base sequence should something like:
>
> #ifdef HAVE_STDINT_H
> #include <stdint.h>
> #else
> # ifdef HAVE_INTTYPES_H
> # include <inttypes.h>
> # else
> typedef unsigned char uint8_t;
> # endif
> #endif
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.
Does gdb_byte, defined in terms of uint8_t, work for you?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-03 22:28 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 [this message]
2005-05-03 22:31 ` Joel Brobecker
2005-05-04 14:45 ` Mark Kettenis
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=20050503222744.GA10500@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.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