From: Tom Tromey <tromey@redhat.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Vladimir Prus <vladimir@codesourcery.com>, gdb@sources.redhat.com
Subject: Re: Registering pretty-printers
Date: Fri, 12 Jun 2009 17:06:00 -0000 [thread overview]
Message-ID: <m3ocst9ybu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090612005149.GA4987@caradoc.them.org> (Daniel Jacobowitz's message of "Thu\, 11 Jun 2009 20\:51\:49 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Paul> Perhaps my proposal for ".gdb_py" section here:
Paul> http://sourceware.org/ml/archer/2008-q4/msg00162.html
Paul> deserves another look?
Daniel> In my opinion, anything that increases the size of the
Daniel> executable is a non-starter.
In addition to this, I think there are a few other problems with this
approach.
First, this requires a gcc update in order to work. Also, it means a
vendor-specific compiler extension in order for the feature to work.
This makes one of Vladimir's problems worse.
Some languages (Java at least) don't have pragmas. (This problem is
not as severe, since you could mix in a C++ CU.)
This approach means recompiling your source whenever you want to
update the printers. This seems to defeat one of the nicest qualities
of using a scripting language.
Tom
next prev parent reply other threads:[~2009-06-12 17:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 23:11 Vladimir Prus
2009-06-10 19:25 ` Tom Tromey
2009-06-11 8:29 ` Vladimir Prus
2009-06-11 17:14 ` Paul Pluzhnikov
2009-06-12 0:52 ` Daniel Jacobowitz
2009-06-12 7:20 ` Vladimir Prus
2009-06-12 16:43 ` Doug Evans
2009-06-12 16:51 ` Daniel Jacobowitz
2009-06-12 17:12 ` Doug Evans
2009-06-12 17:06 ` Tom Tromey [this message]
2009-06-12 17:36 ` Tom Tromey
2009-06-12 17:43 ` Vladimir Prus
2009-06-15 20:23 ` Tom Tromey
2009-06-26 20:37 ` Tom Tromey
2009-06-27 10:16 ` Vladimir Prus
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=m3ocst9ybu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=ppluzhnikov@google.com \
--cc=vladimir@codesourcery.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