Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
		mathieu lacage <Mathieu.Lacage@sophia.inria.fr>,
	gdb@sourceware.org
Subject: Re: [RFC] Signed/unsigned character arrays are not strings
Date: Tue, 27 Feb 2007 12:02:00 -0000	[thread overview]
Message-ID: <17892.4014.160191.285423@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20070226004457.GA9926@caradoc.them.org>

 > > Which GDB behavior is better is a matter of how often each one is
 > > convenient and how often it causes trouble.  I don't know enough to
 > > have an opinion about that, but if neither one is clearly better
 > > overall, it would be best to leave GDB the way it was.
 > 
 > For myself, I think the new behavior is clearly better overall, and
 > that relatively few packages rely on sign-specified character types
 > for strings; that's why I approved Jan's patch.  I even proposed an
 > extension that I would find even more useful, to suppress the
 > single-quoted characters for arrays of signed or unsigned byte
 > variables.  (No one's commented on that; I'll wait until we decide
 > about this one first.)
 > 
 > Do you think that Emacs's behavior - an important GNU application, but
 > only one - changes the overall situation?  I don't, and I am generally
 > opposed to backing this change out.  

I'm not sure who you are addressing, but I don't think anyone is saying
Emacs changes the overall situation.

 >                                      I believe there are more
 > applications which use single byte arrays for numerical data than for
 > character data.  

That answers the question that we are really asking and justifies the patch.

 >                 We can document how to produce string output more
 > clearly in the manual, perhaps?

Yes I think that is important, especially for an incompatible change.

The following could also be updated in the manual:

         (gdb) print $xmm1
         $1 = {
           v4_float = {0, 3.43859137e-038, 1.54142831e-044, 1.821688e-044},
           v2_double = {9.92129282474342e-303, 2.7585945287983262e-313},
           v16_int8 = "\000\000\000\000\3706;\001\v\000\000\000\r\000\000",
           v8_int16 = {0, 0, 14072, 315, 11, 0, 13, 0},
           v4_int32 = {0, 20657912, 11, 13},
           v2_int64 = {88725056443645952, 55834574859},
           uint128 = 0x0000000d0000000b013b36f800000000
         }

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2007-02-27 11:02 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-24 16:13 Nick Roberts
2007-02-24 20:11 ` Daniel Jacobowitz
2007-02-24 20:53   ` Nick Roberts
2007-02-24 21:07     ` Jan Kratochvil
2007-02-25  8:00       ` Daniel Jacobowitz
2007-02-25 19:54         ` Nick Roberts
2007-02-25 21:07     ` mathieu lacage
2007-02-26  0:45       ` Jan Kratochvil
2007-02-27  7:17         ` Eli Zaretskii
2007-02-27  9:29         ` Daniel Jacobowitz
2007-02-27 12:02           ` Nick Roberts [this message]
2007-02-27 17:06             ` Robert Dewar
2007-02-27 18:42               ` Daniel Jacobowitz
2007-02-27 21:53                 ` Eli Zaretskii
2007-02-27 22:12                   ` Daniel Jacobowitz
2007-02-27 22:14                     ` Mark Kettenis
2007-02-28  0:47                       ` Paul Koning
2007-02-28  1:14                       ` Jim Blandy
2007-02-28  1:59                         ` Jim Blandy
2007-02-28  5:26                           ` Nick Roberts
2007-02-28 14:35                       ` Daniel Jacobowitz
2007-03-01  0:43                         ` Jim Blandy
2007-03-01  0:54                         ` Nick Roberts
2007-02-27 21:47               ` Eli Zaretskii
2007-02-27 22:12             ` Daniel Jacobowitz
2007-04-10 21:59         ` Daniel Jacobowitz
2007-02-28 13:05 pkoning
2007-03-01 11:01 ` Mark Kettenis

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=17892.4014.160191.285423@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=Mathieu.Lacage@sophia.inria.fr \
    --cc=drow@false.org \
    --cc=gdb@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