Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 0/5] Some random C++-ification
Date: Thu, 22 Sep 2016 19:10:00 -0000	[thread overview]
Message-ID: <1ee37f8c-0c1a-7368-4cea-96bbbf43a2af@redhat.com> (raw)
In-Reply-To: <1474566656-15389-1-git-send-email-tom@tromey.com>

On 09/22/2016 06:50 PM, Tom Tromey wrote:
> I was feeling inspired by Pedro's Cauldron slides, so I found a few

Awesome!  :-)

> random spots that could be converted from cleanups to self-managing
> data structures from libstdc++ -- in these cases, std::string and
> std::vector.
> 
> I saw a note in one of the C++ conversion documents about perhaps not
> using std::vector, since GCC did not.  However, I think often GCC's
> uses are unusual, and I don't think there is any reason to avoid
> std::vector in (most of) gdb.

Agreed.

> 
> This should probably not go in until after Pedro's "new" patch.

Does that patch look OK to you?

> 
> Built and regtested on x86-64 Fedora 24.
> 
> A few reflections on these changes:
> 
> * First, I think it's a nice improvement.  The examples here aren't so
>   dramatic, but if you dig a bit it's easy to find cases where the
>   cleanup logic is complicated; and this approach eventually lets one
>   delegate all that work to the compiler.

Agreed.

> 
> * Speaking of, I have a patch to convert uses of the ensure_python_env
>   to use RAII.  However, I don't think this is ready to go in --
>   because the cleanups installed by this are order-sensitive with
>   respect to other cleanups that might be created in the various
>   Python-calling functions.  My belief is that cleanups have to all be
>   run before any destructors, so any ordering issues are a subtlety
>   that, in the short term, will have to be accounted for in code
>   review.
> 
> * It wasn't actually clear to me that this kind of change is
>   desirable.

I think it is.  We need to eliminate _all_ cleanups in order to
get rid of the TRY/CATCH macros...  I think there's a lot of
value in getting the codebase rid of the C -> C++ partial
transition and inviting to work on.

> 
> * I was unclear on the coding style to use so I just used the gdb C
>   style.  Maybe there are some spaces that shouldn't be there now.

Looked fine to me.

Thanks,
Pedro Alves


  parent reply	other threads:[~2016-09-22 19:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 17:51 Tom Tromey
2016-09-22 17:51 ` [RFA 1/5] Use std::string in break-catch-sig.c Tom Tromey
2016-09-23 13:17   ` Yao Qi
2016-09-22 17:51 ` [RFA 3/5] Use std::string, std::vector in rust-lang.c Tom Tromey
2016-09-22 19:03   ` Pedro Alves
2016-09-22 19:24     ` Tom Tromey
2016-09-22 19:35       ` Pedro Alves
2016-09-22 20:37         ` Pierre Muller
     [not found]         ` <57e4328a.c3c4620a.59d5b.803fSMTPIN_ADDED_BROKEN@mx.google.com>
2016-09-23  9:44           ` Pedro Alves
2016-09-23 15:56             ` Tom Tromey
2016-09-23 16:15               ` Pedro Alves
2016-09-22 17:51 ` [RFA 2/5] Use std::string in cp-namespace.c Tom Tromey
2016-09-22 19:08   ` Pedro Alves
2016-09-22 20:56     ` Tom Tromey
2016-09-22 17:51 ` [RFA 4/5] Use std::vector in objfiles.c Tom Tromey
2016-09-22 19:03 ` [RFA 5/5] Use std::string rather than dyn-string Tom Tromey
2016-09-22 19:10 ` Pedro Alves [this message]
2016-09-22 19:15   ` [RFA 0/5] Some random C++-ification Pedro Alves
2016-09-22 23:10   ` Trevor Saunders
2016-09-23 15:47   ` Tom Tromey
2016-09-23 15:49     ` 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=1ee37f8c-0c1a-7368-4cea-96bbbf43a2af@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