Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@linaro.org>
To: Pedro Alves <pedro@palves.net>,
	Christian Biesinger <cbiesinger@google.com>,
	Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: make inferior::terminal a unique ptr
Date: Thu, 25 Jun 2020 14:59:35 -0300	[thread overview]
Message-ID: <7ae6c907-4507-e0c3-3a52-6416a8203987@linaro.org> (raw)
In-Reply-To: <5b6a39ca-b29e-262b-1f0c-04fbd21a0c31@palves.net>

On 6/25/20 2:28 PM, Pedro Alves wrote:
> On 6/25/20 6:18 PM, Christian Biesinger via Gdb-patches wrote:
>> On Thu, Jun 25, 2020 at 10:55 AM Simon Marchi via Gdb-patches
>> <gdb-patches@sourceware.org> wrote:
>>> -    current_inferior ()->terminal = xstrdup (terminal_name);
>>> +    current_inferior ()->terminal.reset (xstrdup (terminal_name));
>>
>> Perhaps it really should be a std::string?
> 
> I think there's no good reason for that.  It's a string that doesn't
> ever need to grow/shrink.  And then its use is to pass down to
> a syscall that accepts C-style null-terminated strings:

I tend to agree with Christian. I suppose one positive outcome is to 
make the code less cumbersome. It's not like xstrdup is great to read 
anyway.

Are we worried about performance implications of passing std::string's 
around like this?


  reply	other threads:[~2020-06-25 17:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 15:55 Simon Marchi
2020-06-25 17:18 ` Christian Biesinger
2020-06-25 17:28   ` Pedro Alves
2020-06-25 17:59     ` Luis Machado [this message]
2020-06-25 18:09       ` Pedro Alves
2020-06-25 18:39         ` Simon Marchi
2020-06-25 21:20         ` Christian Biesinger
2020-06-25 17:32 ` Pedro Alves
2020-06-25 18:42   ` Simon Marchi
2020-06-25 21:17     ` Pedro Alves
2020-06-25 20:15 ` Tom Tromey
2020-06-25 21:07   ` Simon Marchi
2020-06-25 21:45     ` Tom Tromey

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=7ae6c907-4507-e0c3-3a52-6416a8203987@linaro.org \
    --to=luis.machado@linaro.org \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    --cc=simon.marchi@efficios.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