From: Anthony Green <green@redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: naming command arguments
Date: Thu, 25 Jul 2002 17:48:00 -0000 [thread overview]
Message-ID: <1027644539.1965.65.camel@dhcppc2> (raw)
In-Reply-To: <3D408887.70003@ges.redhat.com>
On Thu, 2002-07-25 at 16:23, Andrew Cagney wrote:
> For this specific case, how does one differentiate between:
>
> start:1
>
> the source and line specification and:
>
> start:1
>
> the start:VALUE?
Just by context. And in the case that the command has both optional
source location and numerical arguments _and_ the user has a file name
which clashes with an argument name, you just let the user disambiguate
by using multiple ':', so
start::1
doesn't identify a source location because the user doesn't have a
"start:" file. This seems to be a reasonable solution to what I imagine
will be a very rare problem.
AG
next prev parent reply other threads:[~2002-07-26 0:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 17:14 Anthony Green
2002-07-25 16:23 ` Andrew Cagney
2002-07-25 17:48 ` Anthony Green [this message]
2002-07-26 15:02 ` Michael Snyder
2002-07-29 8:41 ` Andrew Cagney
2002-07-29 8:45 ` Daniel Jacobowitz
2002-07-30 20:32 ` Andrew Cagney
2002-07-30 17:43 ` Fernando Nasser
2002-08-03 21:31 ` Anthony Green
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=1027644539.1965.65.camel@dhcppc2 \
--to=green@redhat.com \
--cc=ac131313@ges.redhat.com \
--cc=gdb@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