public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug rust/20164] fix string printing in rust
Date: Thu, 17 Feb 2022 23:45:23 +0000	[thread overview]
Message-ID: <bug-20164-4717-CUl54Pcu79@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20164-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=20164

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #4 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Tom Tromey from comment #3)
> I wonder if char printing should use unicode-ish syntax like:
> 
> (gdb) print 'x'
> $1 = U+0078 'x'
> 
> Not sure.

I like it.

Note that the convention is to have zeros prepended when there are less than 4
digits, but not when there are 5 or 6 digits.
https://www.unicode.org/versions/Unicode14.0.0/appA.pdf
"Leading zeros are omitted, unless the code point would have fewer than four
hexadecimal digits — for example, U+0001, U+0012, U+0123, U+1234, U+12345,
U+102345."

I am not sure how to flag the "illegal" char values, U+D800 to U+DFFF and
anything larger than U+10FFFF. But it would be good to have some indicator you
are dealing with an invalid value.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-02-17 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-20164-4717@http.sourceware.org/bugzilla/>
2022-02-13 18:03 ` tromey at sourceware dot org
2022-02-17 23:15 ` tromey at sourceware dot org
2022-02-17 23:45 ` mark at klomp dot org [this message]
2022-02-17 23:53 ` tromey at sourceware dot org
2022-02-18  0:10 ` mark at klomp dot org
2022-02-18  0:39 ` tromey at sourceware dot org
2022-02-18  1:04 ` mark at klomp dot org
2022-02-18  1:16 ` tromey at sourceware dot org

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=bug-20164-4717-CUl54Pcu79@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).