From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13044 invoked by alias); 14 Jan 2008 22:33:44 -0000 Received: (qmail 13036 invoked by uid 22791); 14 Jan 2008 22:33:43 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO brahms.sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 14 Jan 2008 22:33:21 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.14.1/8.14.0) with ESMTP id m0EMVqN5018997; Mon, 14 Jan 2008 23:31:52 +0100 (CET) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.14.1/8.14.1/Submit) id m0EMVpT5010078; Mon, 14 Jan 2008 23:31:51 +0100 (CET) Date: Mon, 14 Jan 2008 22:33:00 -0000 Message-Id: <200801142231.m0EMVpT5010078@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: jimb@codesourcery.com CC: eliz@gnu.org, drow@false.org, gdb-patches@sourceware.org In-reply-to: (message from Jim Blandy on Mon, 14 Jan 2008 14:24:55 -0800) Subject: Re: [RFC/RFA?] Should break FILE:LINENO skip prologue? References: <20080111053547.GB12954@adacore.com> <200801111126.m0BBQQDB006618@brahms.sibelius.xs4all.nl> <20080111182136.GD12954@adacore.com> <200801112113.m0BLDnAF024595@brahms.sibelius.xs4all.nl> <200801121531.m0CFVW8I023504@brahms.sibelius.xs4all.nl> <200801121618.m0CGI27U012957@brahms.sibelius.xs4all.nl> <20080112175817.GA21954@caradoc.them.org> <200801130921.m0D9LDtI008394@brahms.sibelius.xs4all.nl> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00333.txt.bz2 > From: Jim Blandy > Date: Mon, 14 Jan 2008 14:24:55 -0800 > > There are three possible approaches: > > a) In Eli's original message, the list include "*EXPRESSION" and > "*FUNCTION" as separate cases. This suggested to me that Eli > thought we should document them as separate cases. > > b) We could document the "*EXPRESSION" case, and then point out the > commonly used "*FUNCTION" usage of that case. > > c) We could document "*EXPRESSION", and not mention "*FUNCTION" at > all. > > I dislike a), because it suggests that "*FUNCTION" is recognized > specially --- it is not. In many languages this doesn't matter, but > as Joel points out, a) would be actively misleading for Ada users, as > "*FUNCTION" does not refer to the first instruction of FUNCTION in > Ada. > > I dislike c), for the reasons Eli mentioned, and because I appreciate > having handy use cases pointed out. > > So b) is my first choice. And b) is exactly what I tried to get across (although it seems I failed). Hopefully this mail from Jim clarifies things.