From: "André Pönitz" <andre.poenitz@nokia.com>
To: ext Tom Tromey <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] 12843
Date: Wed, 31 Aug 2011 08:54:00 -0000 [thread overview]
Message-ID: <201108311054.24074.andre.poenitz@nokia.com> (raw)
In-Reply-To: <m339gidddx.fsf@fleche.redhat.com>
On Tuesday 30 August 2011 19:20:58 ext Tom Tromey wrote:
> >>>>> "André" == André Pönitz <andre.poenitz@nokia.com> writes:
>
> Tom> Do you generate MI-compliant output from Python? I'm curious.
>
> André> Sort of. Originally it was fully compliant, then extra fields had been
> André> added and additional commas became "legal" (to save a few cycles
> André> for the check whether they are necessary). But it's still pretty MI-ish.
>
> I ask because I occasionally wonder whether it would be useful to add
> support for converting (a subset of) Python objects to MI.
>
> Phil might need it for breakpoint_ops; but I think we were thinking in
> terms of a one-off, where a generic facility might be better.
Having a generic way to serialize gdb's python objects to MI might
be convenient. On the other hand that's generally not too difficult
to do "manually" for some specific case.
It might be also interesting from a performance point of view,
especially if this would be usable for lots of items.
I am not sure how much of a difference this would make, though,
but allowing the "sloppy" commas I mentioned certainly made a
difference, so I guess there's some general potential to gain a
few cycles by doing the formatting in C and not in Python.
Andre'
next prev parent reply other threads:[~2011-08-31 8:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 21:59 Keith Seitz
2011-08-26 18:23 ` Tom Tromey
2011-08-26 18:46 ` Keith Seitz
2011-08-26 19:07 ` Tom Tromey
2011-08-27 8:45 ` Eli Zaretskii
2011-08-27 13:17 ` asmwarrior
2011-08-29 19:18 ` Tom Tromey
2011-08-29 7:19 ` André Pönitz
2011-08-29 10:13 ` Pedro Alves
2011-08-29 12:06 ` Matt Rice
2011-08-29 12:15 ` André Pönitz
2011-08-29 13:53 ` Pedro Alves
2011-08-29 19:21 ` Jan Kratochvil
2011-08-30 8:19 ` André Pönitz
2011-08-30 9:21 ` Jan Kratochvil
2011-08-30 15:02 ` Tom Tromey
2011-08-30 16:34 ` André Pönitz
2011-08-30 17:21 ` Tom Tromey
2011-08-31 8:54 ` André Pönitz [this message]
2011-08-29 19:46 ` Tom Tromey
2011-08-29 21:13 ` Keith Seitz
2011-08-30 2:35 ` Daniel Jacobowitz
2011-08-30 15:00 ` Tom Tromey
2011-08-30 17:24 ` Tom Tromey
2011-08-31 18:17 ` Keith Seitz
2011-08-31 18:23 ` Jan Kratochvil
2011-08-31 18:52 ` Tom Tromey
2011-09-02 16:04 ` asmwarrior
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=201108311054.24074.andre.poenitz@nokia.com \
--to=andre.poenitz@nokia.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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