public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
	Simon Marchi <simon.marchi@ericsson.com>,
	       gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Introduce string_appendf/string_vappendf (Re: [RFA 4/6] Simple cleanup removals in remote.c)
Date: Mon, 30 Oct 2017 00:16:00 -0000	[thread overview]
Message-ID: <29353d541728ec98b62a1622dc3acb38@polymtl.ca> (raw)
In-Reply-To: <6f25988500a233845974f3b99e47a8f9@polymtl.ca>

On 2017-10-18 23:12, Simon Marchi wrote:
> On 2017-10-18 23:11, Simon Marchi wrote:
>>> +
>>> +/* See documentation in common-utils.h.  */
>>> +
>>> +void
>>> +string_appendf (std::string &str, const char *fmt, ...)
>>> +{
>>> +  va_list vp;
>>> +  int grow_size;
>>> +
>>> +  va_start (vp, fmt);
>>> +  grow_size = vsnprintf (NULL, 0, fmt, vp);
>>> +  va_end (vp);
>>> +
>>> +  size_t curr_size = str.size ();
>>> +  str.resize (curr_size + grow_size);
>>> +
>>> +  /* C++11 and later guarantee std::string uses contiguous memory 
>>> and
>>> +     always includes the terminating '\0'.  */
>>> +  va_start (vp, fmt);
>>> +  vsprintf (&str[curr_size], fmt, vp);
>>> +  va_end (vp);
>>> +}
>>> +
>>> +
>>> +/* See documentation in common-utils.h.  */
>>> +
>>> +void
>>> +string_vappendf (std::string &str, const char *fmt, va_list args)
>>> +{
>>> +  va_list vp;
>>> +  int grow_size;
>>> +
>>> +  va_copy (vp, args);
>>> +  grow_size = vsnprintf (NULL, 0, fmt, vp);
>>> +  va_end (vp);
>>> +
>>> +  size_t curr_size = str.size ();
>>> +  str.resize (curr_size + grow_size);
>>> +
>>> +  /* C++11 and later guarantee std::string uses contiguous memory 
>>> and
>>> +     always includes the terminating '\0'.  */
>>> +  vsprintf (&str[curr_size], fmt, args);
>>> +}
>>> +
>> 
>> string_appendf can be implemented using string_vappendf, to reduce
>> duplication.  It would basically be like string_vappendf_wrapper is.
>> In the tests, we can probably just test string_appendf then.
>> 
>> Unless there's a good reason for them not sharing code?
> 
> Actually the same comment would apply to string_{v,}printf.
> 
> Simon

Hi Pedro,

I came across a case where string_appendf would be useful, so I was 
wondering if you intended to push this patch.  If you don't have the 
time, I would be happy to take care of it, just tell me if you agree 
with my comments and I'll make the changes & push.

Simon

  reply	other threads:[~2017-10-30  0:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16  3:04 [RFA 0/6] more cleanup removals Tom Tromey
2017-10-16  3:04 ` [RFA 5/6] Return unique_xmalloc_ptr from target_read_stralloc Tom Tromey
2017-10-16 21:02   ` Simon Marchi
2017-10-16  3:04 ` [RFA 2/6] Remove some cleanups from probe.c Tom Tromey
2017-10-16 20:26   ` Simon Marchi
2017-10-16  3:04 ` [RFA 4/6] Simple cleanup removals in remote.c Tom Tromey
2017-10-16 20:43   ` Simon Marchi
2017-10-16 21:14     ` Tom Tromey
2017-10-16 21:37       ` Simon Marchi
2017-10-16 21:50         ` Tom Tromey
2017-10-16 22:35         ` Pedro Alves
2017-10-16 23:00           ` Tom Tromey
2017-10-16 23:34             ` [PATCH 1/2] Introduce string_appendf/string_vappendf (Re: [RFA 4/6] Simple cleanup removals in remote.c) Pedro Alves
2017-10-19  3:11               ` Simon Marchi
2017-10-19  3:13                 ` Simon Marchi
2017-10-30  0:16                   ` Simon Marchi [this message]
2017-10-30 11:48                 ` Pedro Alves
2017-10-16 23:38             ` [PATCH 2/2] remote.c, QCatchSyscalls: Build std::string instead of unique_xmalloc_ptr " Pedro Alves
2017-10-19  3:17               ` Simon Marchi
2017-10-30 11:49                 ` Pedro Alves
2017-10-16  3:04 ` [RFA 6/6] Return unique_xmalloc_ptr from target_fileio_read_stralloc Tom Tromey
2017-10-16 21:07   ` Simon Marchi
2017-10-16  3:04 ` [RFA 1/6] Use std::vector in end_symtab_get_static_block Tom Tromey
2017-10-16 20:18   ` Simon Marchi
2017-10-16 21:59     ` Tom Tromey
2017-10-20 15:33       ` Ulrich Weigand
2017-10-20 16:47         ` Pedro Alves
2017-10-23 16:16           ` Ulrich Weigand
2017-10-24 13:55             ` Tom Tromey
2017-10-24 14:41               ` [pushed] " Ulrich Weigand
2017-10-16  3:04 ` [RFA 3/6] Remove cleanup from ppc-linux-nat.c Tom Tromey
2017-10-16 20:28   ` Simon Marchi

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=29353d541728ec98b62a1622dc3acb38@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=simon.marchi@ericsson.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).