From: Dave Brolley <brolley@redhat.com>
To: Dave Brolley <brolley@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: Using vsnprintf or vasprintf in sid
Date: Mon, 26 May 2003 17:28:00 -0000 [thread overview]
Message-ID: <3ED24F16.7010805@redhat.com> (raw)
In-Reply-To: <3ECE6412.7040007@redhat.com>
Thanks Ben and Scott for your suggestions. I do need Solaris support
and, as it turns out, I chose an implementation using a large buffer
with overflow checking, like Scott suggested, until I can figure out how
the autoconf magic works.
Dave
Dave Brolley wrote:
> Hi,
>
> I have a need for printf-like printing into a buffer, however I have
> no control over the input and so I don't know the size of the buffer
> which will be required. It looks like vsnprintf (_ISOC99_SOURCE) or
> vasprintf (_GNU_SOURCE) are what I need. Is it ok to use these
> function in sid and, if so, how do I get configure to add the
> necessary -Dxxxx to the sid compilations and (if necessary) specify
> the library to look in?
>
> Thanks,
> Dave
>
prev parent reply other threads:[~2003-05-26 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 18:17 Dave Brolley
2003-05-26 4:47 ` Ben Elliston
2003-05-26 5:18 ` Scott Dattalo
2003-05-26 17:28 ` Dave Brolley [this message]
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=3ED24F16.7010805@redhat.com \
--to=brolley@redhat.com \
--cc=sid@sources.redhat.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).