From: Joel Brobecker <brobecker@adacore.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: 'Tom Tromey' <tromey@redhat.com>,
"'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [patch] Tweak output of -var-info-path-expression
Date: Fri, 26 Aug 2011 01:48:00 -0000 [thread overview]
Message-ID: <20110826014742.GA2843@adacore.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC578744DD6A@EUSAACMS0703.eamcs.ericsson.se>
> 2011-08-23 Marc Khouzam <marc.khouzam@ericsson.com>
>
> PR mi/11912
> * varobj.c (cplus_describe_child): Add the keyword
> 'class' to the output of the method when dealing
> with a cast to a base class.
>
> 2011-08-23 Marc Khouzam <marc.khouzam@ericsson.com>
>
> PR mi/11912
> * gdb.mi/mi-inheritance-syntax-error.cc: New file.
> * gdb.mi/mi-inheritance-syntax-error.exp: New file.
> * gdb.mi/mi-var-cp.cc: Updated for new 'class'
> keyword in output of -var-info-path-expression.
[...]
> Do you think it is ok for the 7.3 branch?
No objection for putting it on 7.3 since Tom thinks it's OK.
One nit:
> + When we are in the scope of the base class or of one
> + of its children, the type field name will be interpreted
> + as a constructor, if it exists. Therefore, we must
> + indicate that the name is a class name by using the
> + 'class' keyword. PR mi/11912 */
^^^^
Missing second space after a period. I would also follow the general
GCS guideline that everything is a setence, and thus write something
like: `[...] keyword. See PR mi/11912. */'. But that's only if you
agree, it can be seen as a matter of preference.
--
Joel
next prev parent reply other threads:[~2011-08-26 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 13:55 Marc Khouzam
2011-08-10 14:47 ` Tom Tromey
2011-08-23 13:04 ` Marc Khouzam
2011-08-25 17:44 ` Tom Tromey
2011-08-26 1:48 ` Joel Brobecker [this message]
2011-08-26 12:36 ` Marc Khouzam
2011-08-26 20:59 ` [patch] testsuite: unreliable gdb.mi/mi-inheritance-syntax-error.exp [Re: [patch] Tweak output of -var-info-path-expression] Jan Kratochvil
2011-08-26 21:04 ` Tom Tromey
2011-08-26 21:12 ` Jan Kratochvil
2011-08-29 12:16 ` Marc Khouzam
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=20110826014742.GA2843@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=tromey@redhat.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