From: Eli Zaretskii <eliz@gnu.org>
To: Paul Schlie <schlie@comcast.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit] Another gdb_byte pass (correct use?)
Date: Fri, 27 May 2005 13:52:00 -0000 [thread overview]
Message-ID: <ubr6xjevd.fsf@gnu.org> (raw)
In-Reply-To: <BEBC398B.A4AD%schlie@comcast.net> (message from Paul Schlie on Fri, 27 May 2005 02:42:19 -0400)
> Date: Fri, 27 May 2005 02:42:19 -0400
> From: Paul Schlie <schlie@comcast.net>
>
> 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?
Yes.
> as if all 'char's are now 'gdb_byte's, why bother, should have just
> left them alone?
Not all `char *'s are now `gdb_byte's, only thosed where `char *' was
used for something other than a text string.
prev parent reply other threads:[~2005-05-27 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 10:34 Paul Schlie
2005-05-27 13:52 ` Eli Zaretskii [this message]
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=ubr6xjevd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=schlie@comcast.net \
/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