Re: [rfc] python API exposing inferior's frame stack.

[Eli Zaretskii <eliz at gnu dot org>]

> From: Thiago Jung Bauermann <bauerman@br.ibm.com>
> 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.