Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] switch from sprintf to asprintf and snprintf
Date: Sun, 17 Jan 2010 12:59:26 +0100	[thread overview]
Message-ID: <4B52FB9E.3050800@gmail.com> (raw)
In-Reply-To: <20100101093222.GU5847@riva.ucam.org>

[-- Attachment #1: Type: text/plain, Size: 593 bytes --]

Colin Watson wrote:
> On Tue, Dec 29, 2009 at 10:30:12AM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>   
>> +char *EXPORT_FUNC(grub_asprintf) (const char *fmt, ...)
>> +     __attribute__ ((format (printf, 1, 2)));
>>     
>
> It's very confusing that you've made grub_asprintf have a dramatically
> different interface from asprintf. Perhaps you could call this
> grub_xasprintf instead? (Although I notice that it doesn't die when
> malloc fails, but merely returns NULL.)
>   
What about grub_aprintf ?



-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  parent reply	other threads:[~2010-01-17 11:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29  9:30 [PATCH] switch from sprintf to asprintf and snprintf Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-01  9:32 ` Colin Watson
2010-01-01 11:52   ` Robert Millan
2010-01-01 12:01     ` Colin Watson
2010-01-17 12:02     ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-19 22:29       ` Robert Millan
2010-01-19 22:56         ` Colin Watson
2010-01-19 23:16           ` Robert Millan
2010-01-17 11:59   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-01-01 11:51 ` Robert Millan
2010-01-17 12:02   ` Vladimir 'φ-coder/phcoder' Serbinenko

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=4B52FB9E.3050800@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /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