This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: A case for `void *' for pointers to arbitrary (byte) buffers


   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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]