From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26385 invoked by alias); 26 Jul 2002 00:48:59 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26378 invoked from network); 26 Jul 2002 00:48:58 -0000 Received: from unknown (HELO potter.sfbay.redhat.com) (205.180.83.107) by sources.redhat.com with SMTP; 26 Jul 2002 00:48:58 -0000 Received: from dhcp-172-16-25-188.sfbay.redhat.com (vpn3-1.sfbay.redhat.com [172.16.25.1]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g6Q0nDQ02763; Thu, 25 Jul 2002 17:49:13 -0700 Subject: Re: naming command arguments From: Anthony Green To: Andrew Cagney Cc: gdb@sources.redhat.com In-Reply-To: <3D408887.70003@ges.redhat.com> References: <1027556059.2082.179.camel@dhcppc2> <3D408887.70003@ges.redhat.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 25 Jul 2002 17:48:00 -0000 Message-Id: <1027644539.1965.65.camel@dhcppc2> Mime-Version: 1.0 X-SW-Source: 2002-07/txt/msg00275.txt.bz2 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