From: Richard Henderson <rth@redhat.com>
To: Bruce Korb <bruce.korb@gmail.com>, libffi-discuss@sourceware.org
Subject: Re: *printf functions
Date: Fri, 24 Apr 2015 23:24:00 -0000 [thread overview]
Message-ID: <553AD0A8.2040602@redhat.com> (raw)
In-Reply-To: <553ABBA4.40505@gmail.com>
On 04/24/2015 11:54 AM, Bruce Korb wrote:
> Is my hope to use libffi for calling snprintf a vein one?
As long as you used ffi_prep_cif_var instead of ffi_prep_cif it will work. You
didn't quote enough of your source to see that part.
r~
next prev parent reply other threads:[~2015-04-24 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 21:54 Bruce Korb
2015-04-24 23:24 ` Richard Henderson [this message]
2015-04-25 17:31 ` Bruce Korb
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=553AD0A8.2040602@redhat.com \
--to=rth@redhat.com \
--cc=bruce.korb@gmail.com \
--cc=libffi-discuss@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).