From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Tom Tromey <tromey@redhat.com>,
Michael Snyder <msnyder@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: RFC: Inferior command line arguments
Date: Fri, 28 Sep 2001 12:42:00 -0000 [thread overview]
Message-ID: <20010928154217.A17406@nevyn.them.org> (raw)
In-Reply-To: <3BB4CF12.3020900@cygnus.com>
On Fri, Sep 28, 2001 at 03:27:14PM -0400, Andrew Cagney wrote:
>
> Unfortunatly ``--'' already has certain semantics. Detecting it
> wouldn't be sufficient. Consider things like:
>
> --argument-expected --
> -- --poor-programe-name-choice --poor-core-file-choice
> gdb --args -- gdb --args -- program arg arg
>
> Tom's --args -- is somewhat grotesque but at least it is well defined.
> Something like:
>
> gdb --- gdb --- program arg arg
>
> might be possible but it is really sugar for ``--args --''.
As much as I'd prefer '--' (those objections, while completely correct,
could be overcome with a bit of work; I admit I hadn't thought of
them), I'd rather see '---' than --args --, because it doesn't allow
for the confusing semantics of '--args' without the '--'.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-09-28 12:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 21:02 Tom Tromey
2001-09-28 1:31 ` Eli Zaretskii
2001-09-28 5:26 ` Tom Tromey
2001-09-28 7:21 ` Eli Zaretskii
2001-09-28 7:50 ` Tom Tromey
2001-09-28 9:25 ` Eli Zaretskii
2001-09-30 12:07 ` Christopher Faylor
2001-10-01 0:39 ` Eli Zaretskii
2001-10-01 8:07 ` Tom Tromey
2001-10-01 8:10 ` Christopher Faylor
2001-09-28 11:24 ` Michael Snyder
2001-09-28 11:32 ` Tom Tromey
2001-09-28 11:59 ` Daniel Jacobowitz
2001-09-28 12:24 ` Tom Tromey
2001-09-29 2:23 ` Eli Zaretskii
2001-09-28 12:27 ` Andrew Cagney
2001-09-28 12:42 ` Daniel Jacobowitz [this message]
2001-09-28 14:19 ` Tom Tromey
2001-09-28 14:22 ` Daniel Jacobowitz
2001-09-29 1:23 ` David Deephanphongs
2001-10-01 8:09 ` Tom Tromey
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=20010928154217.A17406@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@cygnus.com \
--cc=tromey@redhat.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