This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA][patch 1/9] Yet another respin of the patch with initial Python support
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: tromey at redhat dot com, bauerman at br dot ibm dot com, gdb-patches at sourceware dot org
- Date: Sat, 02 Aug 2008 21:59:26 +0300
- Subject: Re: [RFA][patch 1/9] Yet another respin of the patch with initial Python support
- References: <m3od4z3w0t.fsf@fleche.redhat.com> <m3k5fl3ncy.fsf@fleche.redhat.com> <1216245620.12209.18.camel@localhost.localdomain> <20080718195010.GA14356@caradoc.them.org> <1216653969.31797.6.camel@localhost.localdomain> <uwsj84wx5.fsf@gnu.org> <m3prp0efvr.fsf@fleche.redhat.com> <uhcac4iut.fsf@gnu.org> <20080726182957.GA12363@caradoc.them.org> <uabg44fem.fsf@gnu.org> <20080802173744.GA10333@caradoc.them.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 2 Aug 2008 13:37:44 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: bauerman@br.ibm.com, gdb-patches@sourceware.org
>
> On Sat, Jul 26, 2008 at 10:24:49PM +0300, Eli Zaretskii wrote:
> > > What would you like explained?
> >
> > Why it is important to the manual reader to know that there's a module
> > called `gdb', and that all methods and classes added by GDB are placed
> > in that module. Suppose I didn't know that--what would I be missing
> > as result, and what code would I get wrong?
>
> You would not know that you had to 'import gdb' in any new modules you
> wrote, that's all. This is obvious to a Python programmer from the
> existence of the module.
Might as well say explicitly that new modules need to 'import gdb'.
Most Python programmers will still understand that the methods and
classes added by GDB are placed in the `gdb' module, but the
instruction to 'import gdb' is IMO more friendly to those who won't.