public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Pedro Alves <pedro@palves.net>
Cc: David Malcolm <dmalcolm@redhat.com>,  gcc@gcc.gnu.org
Subject: Re: [RFC] Using std::unique_ptr and std::make_unique in our code
Date: Tue, 12 Jul 2022 12:21:50 +0200	[thread overview]
Message-ID: <87zgheskap.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <6f183e53-02b9-9472-a5cc-9c57c5c0e898@palves.net> (Pedro Alves's message of "Mon, 11 Jul 2022 11:56:52 +0100")

* Pedro Alves:

> For example, for the type above, we'd have:
>
>   typedef std::unique_ptr<pending_diagnostic> pending_diagnostic_up;
>
> and then:
>
>  -				    pending_diagnostic *d,
>  +				    pending_diagnostic_up d,
>
> I would suggest GCC have a similar guideline, before people start
> using foo_ptr, bar_unp, quux_p, whatnot diverging styles.

This doesn't seem to provide much benefit over writing

  uP<pending_diagnostic> d;

and with that construct, you don't need to worry about the actual
relationship between pending_diagnostic and pending_diagnostic_up.

I think the GDB situation is different because many of the types do not
have proper destructors, so std::unique_ptr needs a custom deleter.

Thanks,
Florian


  parent reply	other threads:[~2022-07-12 10:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 20:46 David Malcolm
2022-07-08 21:15 ` Gabriel Ravier
2022-07-08 21:16 ` Jonathan Wakely
2022-07-11 10:56 ` Pedro Alves
2022-07-12  0:32   ` David Malcolm
2022-08-10  1:15     ` James K. Lowden
2022-07-12 10:21   ` Florian Weimer [this message]
2022-07-12 10:45     ` Jonathan Wakely
2022-07-12 11:01       ` Pedro Alves
2022-07-12 11:00     ` 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=87zgheskap.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=pedro@palves.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).