From: Ian Lance Taylor <iant@google.com>
To: "Austin\, Alex" <Alex.Austin@spectrumdsi.com>
Cc: "gcc-help\@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: va_arglist
Date: Tue, 02 Dec 2008 15:37:00 -0000 [thread overview]
Message-ID: <m38wqyfv3p.fsf@google.com> (raw)
In-Reply-To: <3DC6D022E7CC5D41A9CA465499463C9E719BD73237@mtk-sms-exch01.digi.com> (Alex Austin's message of "Tue\, 2 Dec 2008 06\:48\:07 -0600")
"Austin, Alex" <Alex.Austin@spectrumdsi.com> writes:
> Is there any way to write code to generate a variable argument list
> and call a variable function?
There is no portable way to do this. You may be able to use the FFI
library. It's distributed with gcc, in the libffi directory.
Ian
prev parent reply other threads:[~2008-12-02 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 12:48 va_arglist Austin, Alex
2008-12-02 13:30 ` va_arglist Harvey Chapman
2008-12-02 15:39 ` va_arglist Austin, Alex
2008-12-02 18:24 ` va_arglist David Daney
2008-12-02 23:27 ` va_arglist Robert William Fuller
2008-12-04 1:37 ` va_arglist Austin, Alex
2008-12-02 15:37 ` Ian Lance Taylor [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=m38wqyfv3p.fsf@google.com \
--to=iant@google.com \
--cc=Alex.Austin@spectrumdsi.com \
--cc=gcc-help@gcc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).