Proposal: --with-gdb-interpreter=... --interpreter=...

Andrew Cagney
Fri Aug 20 18:20:00 GMT 1999 wrote:
> On Thu, 19 Aug 1999 23:05:13 -0700, wrote:
> > On Thu, 19 Aug 1999 10:38:33 +1000, Andrew Cagney <> wrote:
> >
> > > [...]
> > >
> > >     o       a new option ``--interpreter=...'' that can be used
> > >             to specify the interpreter to use during startup.

		Short form ``-i perl''

> > I propose the flag to be simply called -perl, -python, -tcl, -guile etc. In
> > addition to this the flag should take an additional argument which should
> > represent the name of a script in that language. This would allow the user to
> > write full scripts to work with gdb.
> I forgot to say it, but this allows one to write things like:
> #! /bin/gdb -perl

FYI, that should at least be ``--perl'' and:

	#!/bin/gdb --interpreter=perl

would work as well :-)

As to the more important policy question.  How should that option be
specified.  My personal preference is to sub-option it (hence
--interpreter/-i) that way there is uniformity.  The HumanFactors/Style
decision is up to the chief architect.

There is also a second question lurking here.  Should an interpreter be
allowed to add extra options to the command line?  My preference here is
no.  Again, however, it's a question of style.


More information about the Gdb mailing list