From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Signed/unsigned character arrays are not strings
Date: Thu, 25 Jan 2007 04:23:00 -0000 [thread overview]
Message-ID: <u8xfrd9ay.fsf@gnu.org> (raw)
In-Reply-To: <20070125015422.GA19113@host0.dyn.jankratochvil.net> (message from Jan Kratochvil on Thu, 25 Jan 2007 02:54:22 +0100)
> Date: Thu, 25 Jan 2007 02:54:22 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
>
> currently all these types are printed as strings:
> char
> signed char
> unsigned char
> the patch will reduce the printed strings only to
> char
> and the signed/unsigned version gets printed as an array of byte values
> (characters). I hope nobody uses sign-specification for strings.
I must say I'm uneasy about this. Signedness could be random. What
will happen on platforms where `char' is unsigned by default?
Anyway, this change should probably be reflected in the manual, and
perhaps also in NEWS.
> Bugreported by Ulrich Drepper.
What bug? can you show it?
next prev parent reply other threads:[~2007-01-25 4:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 1:54 Jan Kratochvil
2007-01-25 4:23 ` Eli Zaretskii [this message]
2007-01-25 11:32 ` Jan Kratochvil
2007-01-26 8:54 ` Eli Zaretskii
2007-01-26 10:37 ` Jan Kratochvil
2007-01-26 14:44 ` Eli Zaretskii
2007-02-12 22:15 ` Daniel Jacobowitz
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=u8xfrd9ay.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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