From: Eli Zaretskii <eliz@gnu.org>
To: Matt Rice <ratmice@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 6/7] [python] API for macros: Add docs.
Date: Fri, 26 Aug 2011 10:42:00 -0000 [thread overview]
Message-ID: <83sjoofo80.fsf@gnu.org> (raw)
In-Reply-To: <CACTLOFo-vHqrLWCa8qOJcuYc_u+o1QvqBNNzytY-x7oHH97_kg@mail.gmail.com>
> Date: Fri, 26 Aug 2011 01:04:21 -0700
> From: Matt Rice <ratmice@gmail.com>
> Cc: gdb-patches@sourceware.org
>
> >> macro1.c:18 <gdb.Macro AMACRO
> >> include_trail=[('/home/ratmice/tests/macro1.h', 1),
> >> ('/home/ratmice/tests/macro1.c', 1)]>
> >> macro1.c:18 <gdb.Macro C include_trail=[('/home/ratmice/tests/macro1.c', 16)]>
> >> macro1.c:18 <gdb.Macro B=1 include_trail=[('/home/ratmice/tests/macro1.c', 13)]>
> > [...]
> >> > Â Returns all of the macros which are in effect for the source line
> >> > Â given by the @code{gdb.Symtab_and_line}'s @code{line} attribute.
> >>
> >> The problem I was trying to avoid (and which made my documentation for
> >> this method admittedly crappy), is that your rephrased definition
> >> seems to be plausible for the case when the user wants (C) in the
> >> macro1.c:18 case,
> >> e.g. the macros which are used ON the line. Â When Symtab_and_line.macros()
> >> outputs all of the macros which were defined before the line, which
> >> are still in effect.
> >
> > Sorry, I don't follow. Â Did you mean "B" instead of "C"? Â What is the
> > problem you see here with "C"? Â It is defined only once, on line 16,
> > and so is in effect on line 18. Â I see no issues here. Â What am I
> > missing?
>
> No, I mean "C".
>
> >> macro1.c:18: Â foo(); C; return 0;
>
> So say we are stopped on this line, and have Symtab_and_line for it.
> the user wants to know `all the macros that are used at this source location'
> In this case the answer would be 'C', and my concern is that 'which
> are in effect'
> can be misconstrued. e.g. with the above line in isolation, is 'C' in effect?
Now I'm utterly confused. The output of `macros' shows not just C,
but also AMACRO and B. All of them are "in effect" in line 18. So
why are you talking only about C? The fact that it's actually
mentioned in that line seems irrelevant, because you are documenting
what the `macros' method returns. What am I missing here?
> how about the following.
>
> Returns all of the macros defined before the source line given by the
> @code{gdb.Symtab_and_line}'s @code{line} attribute which are in still
> effect.
How is this different from my suggestion above?
> >> >> +@defmethod Symtab macros
> >> >> +Return all of the macros contained in the symbol table.
> >> >> +@end defmethod
> >> >
> >> > Return what, exactly? only their names? something else?
> >>
> >> i'll try 'Return a list of macro objects for all of the macros
> >> contained in the symbol table.'
> >
> > Based on the example above (which I highly recommend to have in the
> > manual), I'd say "a list of macro objects with their values and
> > include trail".
>
> hrm, except what is above is the output of the string function,
> if you actually print the return value without converting to a string
> it prints something like (<gdb.Macro 0x.......>, <gdb.Macro 0x.....>),
What are the 0x.... numbers here?
next prev parent reply other threads:[~2011-08-26 10:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 15:11 [PATCH 0/7] [python] API for macros matt rice
2011-08-24 15:11 ` [PATCH 1/7] [python] API for macros: abort or continuing macro iterators matt rice
2011-08-26 20:23 ` Tom Tromey
2011-08-30 11:10 ` Phil Muldoon
2011-09-01 21:48 ` Matt Rice
2011-08-24 15:11 ` [PATCH 2/7] [python] API for macros: memory management quirks matt rice
2011-08-26 20:40 ` Tom Tromey
2011-08-30 11:47 ` Phil Muldoon
2011-09-01 22:46 ` Matt Rice
2011-08-24 15:11 ` [PATCH 5/7] [python] API for macros: gdb.Objfile symtabs method matt rice
2011-08-30 13:08 ` Phil Muldoon
2011-09-01 23:18 ` Matt Rice
2011-09-02 1:07 ` Paul_Koning
2011-08-30 17:34 ` Tom Tromey
2011-09-02 0:56 ` Matt Rice
2011-08-24 15:12 ` [PATCH 7/7] [python] API for macros: Add tests matt rice
2011-08-30 13:12 ` Phil Muldoon
2011-08-30 15:54 ` Tom Tromey
2011-08-24 15:12 ` [PATCH 3/7] [python] API for macros: Add gdb.Macro class matt rice
2011-08-30 12:45 ` Phil Muldoon
2011-09-01 22:57 ` Matt Rice
2011-08-24 15:12 ` [PATCH 4/7] [python] API for macros: Add methods to get a gdb.Macro matt rice
2011-08-30 13:04 ` Phil Muldoon
2011-08-30 17:41 ` Tom Tromey
2011-08-30 20:28 ` Phil Muldoon
2011-08-30 20:35 ` Phil Muldoon
2011-09-01 23:13 ` Matt Rice
2011-09-02 1:15 ` Paul_Koning
2011-09-02 10:04 ` Paul_Koning
2011-09-02 12:04 ` Phil Muldoon
2011-08-30 20:38 ` Tom Tromey
2011-08-30 20:58 ` Phil Muldoon
2011-08-24 15:12 ` [PATCH 6/7] [python] API for macros: Add docs matt rice
2011-08-24 20:10 ` Eli Zaretskii
2011-08-25 12:33 ` Matt Rice
2011-08-25 17:36 ` Eli Zaretskii
2011-08-26 8:04 ` Matt Rice
2011-08-26 10:42 ` Eli Zaretskii [this message]
2011-08-26 11:17 ` Matt Rice
2011-08-26 12:08 ` Eli Zaretskii
2011-08-26 14:06 ` Matt Rice
2011-08-26 15:05 ` Eli Zaretskii
2011-08-30 9:44 ` [PATCH 0/7] [python] API for macros Phil Muldoon
2011-09-01 21:33 ` Matt Rice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sjoofo80.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ratmice@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox