From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFA/python:2/2] First script in GDB python library - command/pahole.py
Date: Sun, 11 Jul 2010 18:49:00 -0000 [thread overview]
Message-ID: <m3vd8lyhu2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100603153459.GK3019@adacore.com> (Joel Brobecker's message of "Thu, 3 Jun 2010 08:34:59 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> I think that if we want to have help and apropos working, we might
Joel> as well just use the simpler approach of running the command scripts
Joel> right from the start.
I have been thinking more about this problem recently.
One idea is KISS: just load all the commands and functions at startup.
I avoided this initially out of fear that it would be too slow -- but I
never measured it. Maybe it isn't so bad.
A second idea is to install the Command objects eagerly, but have the
implementation lazily load the actual code. That is, there would be a
single Command subclass that would take a help string, a module name,
and a class name (string) arguments, and then when the user invoked the
command it would import the module and instantiate an object to which
the command operations would be delegated.
This approach would work for convenience functions, too. It is also
easy for 3rd party users to use.
Also, we can always start with KISS and move to the lazier approach if
it turns out to be too slow.
Tom
next prev parent reply other threads:[~2010-07-11 18:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 0:09 Add support for the GDB Python Library Joel Brobecker
2010-05-27 0:09 ` [RFA/python:2/2] First script in GDB python library - command/pahole.py Joel Brobecker
2010-05-27 20:37 ` Tom Tromey
2010-05-28 1:34 ` Joel Brobecker
2010-06-03 0:11 ` Joel Brobecker
2010-06-03 6:28 ` Doug Evans
2010-06-03 15:35 ` Joel Brobecker
2010-07-11 18:49 ` Tom Tromey [this message]
2010-05-27 0:25 ` [RFA/python:1/2] Add support for --with-pythondir Joel Brobecker
2010-05-27 6:49 ` Doug Evans
2010-05-27 20:32 ` Tom Tromey
2010-05-28 9:55 ` Doug Evans
2010-05-28 17:20 ` Joel Brobecker
2010-05-30 17:10 ` Doug Evans
2010-06-01 20:15 ` Joel Brobecker
2010-06-01 20:39 ` Doug Evans
2010-06-01 20:53 ` Joel Brobecker
2010-05-27 1:54 ` Add support for the GDB Python Library Doug Evans
2010-05-27 3:42 ` Doug Evans
2010-05-27 15:17 ` Joel Brobecker
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=m3vd8lyhu2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@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