From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: [users/palves/format_strings] %pS/%pN -> %p[/%p]
Date: Mon, 01 Jul 2019 19:27:00 -0000 [thread overview]
Message-ID: <8216adbc-9d34-a29a-02e3-42e0a1ef49fb@redhat.com> (raw)
In-Reply-To: <87muhxpt7q.fsf@tromey.com>
On 7/1/19 6:20 PM, Tom Tromey wrote:
>>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
>
> Pedro> The visual balance of brackets is appealing as well, so I can't say
> Pedro> I have a strong preference either way. If you've been converting things
> Pedro> already, you'll have a better judgment, so I'll defer to you.
>
> I haven't really converted much, just what you saw on the branch.
>
> I suspect using some kind of paired brackets will make it a little
> harder to forget to close the style. But probably only a little. Also
> I guess we could add asserts to check that the closing parameter is
> always null.
Let's try this. I pushed the patch below to the branch.
From 5984c619b7ee91e6414b1a56d0a735240fb5afce Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Mon, 1 Jul 2019 19:07:44 +0100
Subject: [PATCH] %pS/%pN -> %p[/%p]
---
gdb/common/format.c | 3 ++-
gdb/ui-out.c | 12 ++++++++----
2 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/gdb/common/format.c b/gdb/common/format.c
index 177f79afee3..345bdfc4cca 100644
--- a/gdb/common/format.c
+++ b/gdb/common/format.c
@@ -259,7 +259,8 @@ format_pieces::format_pieces (const char **arg, bool gdb_extensions)
case 's':
case 'S':
case 'F':
- case 'N':
+ case '[':
+ case ']':
f++;
break;
}
diff --git a/gdb/ui-out.c b/gdb/ui-out.c
index d50fb3a3e3f..065a9209656 100644
--- a/gdb/ui-out.c
+++ b/gdb/ui-out.c
@@ -617,12 +617,16 @@ ui_out::vmessage (const char *format, va_list args)
call_do_message (ss->style (), "%s", ss->str ());
}
break;
- case 'S':
+ case '[':
style = *va_arg (args, const ui_file_style *);
break;
- case 'N':
- va_arg (args, void *);
- style = {};
+ case ']':
+ {
+ void *arg = va_arg (args, void *);
+ gdb_assert (arg == nullptr);
+
+ style = {};
+ }
break;
default:
call_do_message (style, current_substring, va_arg (args, void *));
--
2.14.5
next prev parent reply other threads:[~2019-07-01 19:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 2:01 [PATCH] Style "pwd" output Tom Tromey
2019-06-05 8:36 ` Pedro Alves
2019-06-05 13:42 ` Tom Tromey
2019-06-05 15:21 ` Pedro Alves
2019-06-05 18:12 ` ui_out format strings for fields and styles (Re: [PATCH] Style "pwd" output) Pedro Alves
2019-06-05 20:27 ` Tom Tromey
2019-06-05 20:39 ` Pedro Alves
2019-06-05 20:42 ` Pedro Alves
2019-06-05 20:49 ` Tom Tromey
2019-06-05 20:47 ` Tom Tromey
2019-06-05 21:25 ` Pedro Alves
2019-06-05 22:21 ` Tom Tromey
2019-06-06 15:49 ` Pedro Alves
2019-06-06 23:55 ` Tom Tromey
2019-06-07 18:27 ` Tom Tromey
2019-06-07 19:20 ` Tom Tromey
2019-07-01 12:23 ` Pedro Alves
2019-07-01 12:55 ` Pedro Alves
2019-07-01 13:06 ` Pedro Alves
2019-07-01 17:26 ` Tom Tromey
2019-07-01 19:24 ` [users/palves/format_strings] Down with .ptr() (Re: ui_out format strings for fields and styles (Re: [PATCH] Style "pwd" output)) Pedro Alves
2019-07-01 13:17 ` ui_out format strings for fields and styles (Re: [PATCH] Style "pwd" output) Pedro Alves
2019-07-01 13:20 ` Pedro Alves
2019-07-01 17:38 ` Tom Tromey
2019-07-01 18:49 ` Tom Tromey
2019-07-01 18:56 ` Pedro Alves
2019-07-01 19:30 ` [users/palves/format_strings] Document the gdb-specific formatters Pedro Alves
2019-07-01 19:25 ` [users/palves/format_strings] Introduce string_field Pedro Alves
2019-07-01 17:43 ` ui_out format strings for fields and styles (Re: [PATCH] Style "pwd" output) Tom Tromey
2019-07-01 19:29 ` [users/palves/format_strings] Make printf_filtered support the gdb-specific formatters too Pedro Alves
2019-07-01 12:01 ` ui_out format strings for fields and styles (Re: [PATCH] Style "pwd" output) Pedro Alves
2019-07-01 12:25 ` Tom Tromey
2019-07-01 12:37 ` Pedro Alves
2019-07-01 17:20 ` Tom Tromey
2019-07-01 19:27 ` Pedro Alves [this message]
2019-07-01 19:32 ` Philippe Waroquiers
2019-07-03 12:20 ` Tom Tromey
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=8216adbc-9d34-a29a-02e3-42e0a1ef49fb@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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