From: Sergio Durigan Junior <sergiodj@redhat.com>
To: gdb-patches@sourceware.org, tromey@redhat.com
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH] Constify `struct expression' in operator_length
Date: Fri, 04 Jun 2010 21:40:00 -0000 [thread overview]
Message-ID: <201006041840.05417.sergiodj@redhat.com> (raw)
In-Reply-To: <m3r5kmtrfs.fsf@fleche.redhat.com>
On Friday 04 June 2010 18:32:07, Tom Tromey wrote:
> >>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> Due to Joel's suggestion on
> Sergio> <http://sourceware.org/ml/gdb-patches/2010-05/msg00689.html>, I
> Sergio> decided to post this patch in order to constify the `struct
> Sergio> expression' argument of the operator_length class of functions.
>
> Sergio> Ok to apply?
>
> Yes. Thanks for doing this, I think more const-correctness (when
> appropriate, of course) helps make the code more understandable.
Thanks, checked in.
--
Sergio Durigan Junior
Red Hat
prev parent reply other threads:[~2010-06-04 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 21:19 Sergio Durigan Junior
2010-06-04 21:32 ` Tom Tromey
2010-06-04 21:40 ` Sergio Durigan Junior [this message]
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=201006041840.05417.sergiodj@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--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