From: David Deephanphongs <deephan@telocity.com>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: Inferior command line arguments
Date: Sat, 29 Sep 2001 01:23:00 -0000 [thread overview]
Message-ID: <20010929042717.B8313@llamedos.org> (raw)
In-Reply-To: <87vgi3f1f1.fsf@creche.redhat.com>
Thus spake Tom Tromey (tromey@redhat.com):
>
> I'm not really a fan of `---'. It doesn't seem visible enough.
>
> I might be able to make `--args' end argument processing. Then you
> would write:
>
> gdb --args gdb -nw
>
Have you seen my patch? getopt only reorders the arguments that
it has already processed. So, if you detect --args, and break out
of the argument-processing loop, argv[optind] is equal to the
target name, and argv[optind+1] ... argv[argc-1] are the
target's arguments.
How are you handling the fact that you don't know what the target
is until far later in the code?
Dave
--
"The knuckles! The horrible knuckles!"
-- (Terry Pratchett, The Light Fantastic)
next prev parent reply other threads:[~2001-09-29 1:23 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
2001-09-28 14:19 ` Tom Tromey
2001-09-28 14:22 ` Daniel Jacobowitz
2001-09-29 1:23 ` David Deephanphongs [this message]
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=20010929042717.B8313@llamedos.org \
--to=deephan@telocity.com \
--cc=gdb-patches@sources.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