From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [FYI 0/2] C++ in the Rust code
Date: Wed, 09 Nov 2016 23:40:00 -0000 [thread overview]
Message-ID: <30d6a381-950e-9be3-e4d0-1102f25b8e38@redhat.com> (raw)
In-Reply-To: <1478732828-14454-1-git-send-email-tom@tromey.com>
On 11/09/2016 11:07 PM, Tom Tromey wrote:
>
> There are still some cleanups left, primarily due to the way memory is
> managed when parsing; but also a couple because other gdb modules
> haven't yet been converted (e.g., make_cleanup_ui_file_delete).
make_cleanup_ui_file_delete is gone on my
users/palves/cxx-eliminate-cleanups
branch. But before posting that I need to propose making
use of gnulib's C++ namespace support. And before that, I
need to actually fix gnulib'c C++ namespace support...
FWIW, I read the patches and both LGTM.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-11-09 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 23:07 Tom Tromey
2016-11-09 23:07 ` [FYI 1/2] Use std::string in rust_get_disr_info Tom Tromey
2016-11-09 23:07 ` [FYI 2/2] Remove some cleanups from the rust code Tom Tromey
2016-11-09 23:40 ` Pedro Alves [this message]
2016-11-10 0:32 ` [FYI 0/2] C++ in the Rust code Pedro Alves
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=30d6a381-950e-9be3-e4d0-1102f25b8e38@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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