From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22742 invoked by alias); 16 Mar 2009 04:00:22 -0000 Received: (qmail 22730 invoked by uid 22791); 16 Mar 2009 04:00:20 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout6.012.net.il (HELO mtaout6.012.net.il) (84.95.2.16) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 16 Mar 2009 04:00:14 +0000 Received: from conversion-daemon.i-mtaout6.012.net.il by i-mtaout6.012.net.il (HyperSendmail v2007.08) id <0KGK00600YEBOF00@i-mtaout6.012.net.il> for gdb-patches@sourceware.org; Mon, 16 Mar 2009 06:00:54 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.127.228.91]) by i-mtaout6.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KGK00NYKZ5C55G0@i-mtaout6.012.net.il>; Mon, 16 Mar 2009 06:00:49 +0200 (IST) Date: Mon, 16 Mar 2009 04:07:00 -0000 From: Eli Zaretskii Subject: Re: [rfc] python API exposing inferior's frame stack. In-reply-to: <1237160806.8098.8.camel@localhost.localdomain> To: Thiago Jung Bauermann Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: References: <1236706351.11106.17.camel@localhost.localdomain> <1237133466.316.16.camel@localhost.localdomain> <1237160806.8098.8.camel@localhost.localdomain> X-IsSubscribed: yes 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: 2009-03/txt/msg00249.txt.bz2 > From: Thiago Jung Bauermann > Cc: gdb-patches@sourceware.org > Date: Sun, 15 Mar 2009 20:46:46 -0300 > > > I prefer "frames previous to this one". We already use similar > > wording in frame_stop_reason_string. > > I don't like "previous" and "next". They are not clear enough. I think > you prefer this only because you're used to its meaning in the GDB > source code. Not only in the code, in the messages we display to the user, which is quite another thing. > In the doc strings and documentation, I also use "outer" and > "inner", which I still think conforms to be stack chapter in the GDB > manual. As I explained, "outer" or "inner" are almost unused in the manual. We use "innermost" and "outermost". > > We use "innermost" in the manual much more than "inner". You can also > > use "previous" and "next" if you like that better. > > Why "innermost" is acceptable but "inner" is not? Because the former is used a lot in the manual and explained in several places.