From: Paul Schlie <schlie@comcast.net>
To: <gdb-patches@sources.redhat.com>
Subject: Re: [commit] Another gdb_byte pass (correct use?)
Date: Fri, 27 May 2005 10:34:00 -0000 [thread overview]
Message-ID: <BEBC398B.A4AD%schlie@comcast.net> (raw)
Just to double check, as I thought the original intent of gdb_byte* was
an alternative to a void* to more accurately identify byte oriented data
not true char* or char[] strings? as if all 'char's are now 'gdb_byte's,
why bother, should have just left them alone?
(and compiled with unsigned char, or possibly get rid of the silly GCC
warning complaining about comparison of pointers to types differing in
signness, as the types are compatible.)
next reply other threads:[~2005-05-27 6:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 10:34 Paul Schlie [this message]
2005-05-27 13:52 ` Eli Zaretskii
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=BEBC398B.A4AD%schlie@comcast.net \
--to=schlie@comcast.net \
--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