From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-53466-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 3053 invoked by alias); 20 Jan 2008 19:50:45 -0000
Received: (qmail 3040 invoked by uid 22791); 20 Jan 2008 19:50:44 -0000
X-Spam-Check-By: sourceware.org
Received: from nitzan.inter.net.il (HELO nitzan.inter.net.il) (213.8.233.22)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 20 Jan 2008 19:50:25 +0000
Received: from HOME-C4E4A596F7 (IGLD-84-228-46-33.inter.net.il [84.228.46.33]) 	by nitzan.inter.net.il (MOS 3.7.3a-GA) 	with ESMTP id IXT09490 (AUTH halo1); 	Sun, 20 Jan 2008 21:47:49 +0200 (IST)
Date: Sun, 20 Jan 2008 19:50:00 -0000
Message-Id: <uk5m4nuo6.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
CC: jimb@codesourcery.com, mark.kettenis@xs4all.nl, uweigand@de.ibm.com,         msnyder@specifix.com, gdb-patches@sourceware.org
In-reply-to: <20080120150224.GI28020@adacore.com> (message from Joel Brobecker 	on Sun, 20 Jan 2008 07:02:24 -0800)
Subject: Re: [RFC/RFA?] Should break FILE:LINENO skip prologue?
Reply-to: Eli Zaretskii <eliz@gnu.org>
References: <200801152140.m0FLeMha003566@d12av02.megacenter.de.ibm.com> <ur6gipfjm.fsf@gnu.org> <200801161034.m0GAYfpk000326@brahms.sibelius.xs4all.nl> <ulk6pppje.fsf@gnu.org> <m3ir1t78s4.fsf@codesourcery.com> <uejchozs8.fsf@gnu.org> <m3ir1snvqy.fsf@codesourcery.com> <uwsq6nd0d.fsf@gnu.org> <20080120150224.GI28020@adacore.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2008-01/txt/msg00498.txt.bz2

> Date: Sun, 20 Jan 2008 07:02:24 -0800
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Jim Blandy <jimb@codesourcery.com>, mark.kettenis@xs4all.nl,
> 	uweigand@de.ibm.com, msnyder@specifix.com,
> 	gdb-patches@sourceware.org
> 
> >  @item @var{function}
> >  Specifies the line that begins the body of the function @var{function}.
> > -For example: in C, this is the line with the open brace.
> > +For example, in C, this is the line with the open brace.
> 
> This is actually not true. It's usually the first line of code
> past the open brace.

You seem to be thinking about source code formatted according to GNU
coding standards ;-) But C allows code to appear on the same line as
the open brace, so it's not simple to say this with absolute accuracy.
I think on balance, the current wording is not bad: after all, why
should a GDB user care whether the brace itself does or does not
generate executable code?

> > As a convenience, @value{GDBN} extends the semantics of
> > +expressions used in locations to cover the situations that frequently
> > +happen during debugging.
> 
> I was a little bit confused at first by this sentence, as I thought
> that you were saying that all the forms you are describing later are
> extensions, which as you explain for C/C++/etc is not the case.
> At the same time, I found it pretty hard to try to do better.

How about if I say that the extension is in addition to the ``normal''
expression syntax?  Like this:

  Here @var{address} may be any expression valid in the current working
  language (@pxref{Languages, working language}) that specifies a code
  address.  In addition, as a convenience, @value{GDBN} extends the
  semantics of expressions...