From: Andrew Cagney <ac131313@cygnus.com>
To: ovidiu@cup.hp.com
Cc: gdb@sourceware.cygnus.com, insight@sourceware.cygnus.com
Subject: Re: Proposal: --with-gdb-interpreter=... --interpreter=...
Date: Fri, 20 Aug 1999 18:20:00 -0000 [thread overview]
Message-ID: <37BDFDE5.769E6ADD@cygnus.com> (raw)
In-Reply-To: <199908201721.KAA07605@hercules.cup.hp.com>
ovidiu@cup.hp.com wrote:
>
> On Thu, 19 Aug 1999 23:05:13 -0700, ovidiu@cup.hp.com wrote:
>
> > On Thu, 19 Aug 1999 10:38:33 +1000, Andrew Cagney <ac131313@cygnus.com> 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.
enjoy,
Andrew
prev parent reply other threads:[~1999-08-20 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-18 17:39 Andrew Cagney
1999-08-18 17:53 ` Stan Shebs
1999-08-19 3:29 ` Andrew Cagney
1999-08-19 19:30 ` Jim Blandy
1999-08-20 18:35 ` Andrew Cagney
1999-08-19 23:07 ` ovidiu
1999-08-20 10:22 ` ovidiu
1999-08-20 18:20 ` Andrew Cagney [this message]
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=37BDFDE5.769E6ADD@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=insight@sourceware.cygnus.com \
--cc=ovidiu@cup.hp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).