Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Fri, 26 Jan 2007 08:54:00 -0000	[thread overview]
Message-ID: <u1wlicgnj.fsf@gnu.org> (raw)
In-Reply-To: <20070125113206.GA26448@host0.dyn.jankratochvil.net> (message 	from Jan Kratochvil on Thu, 25 Jan 2007 12:32:06 +0100)

> Date: Thu, 25 Jan 2007 12:32:06 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org
> > 
> > I must say I'm uneasy about this.  Signedness could be random.  What
> > will happen on platforms where `char' is unsigned by default?
> 
> I had to find an answer to your interesting comment now myself:
> 
> # The string identification works despite the compiler flags below due to
> # gdbtypes.c:
> #   if (name && strcmp (name, "char") == 0)
> #     TYPE_FLAGS (type) |= TYPE_FLAG_NOSIGN;

Thanks, I withdraw my objections.

> +@code{-funsigned-char} @value{GCC} options have no effect as @value{GDBN}

Please use @value{NGCC}, not @value{GCC}.  The former produces output
similar to @value{GDBN}, the latter produces a literal lowercase "gcc".

> +* Arrays of specifically SIGNED or UNSIGNED CHARs are now printed as arrays
> +  of numbers.

I think "explicitly SIGNED or UNSIGNED..." is a better wording.

Thanks.


  reply	other threads:[~2007-01-26  8:54 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
2007-01-25 11:32   ` Jan Kratochvil
2007-01-26  8:54     ` Eli Zaretskii [this message]
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=u1wlicgnj.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