guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SCM_CALL_N


From: Lars J. Aas
Subject: Re: SCM_CALL_N
Date: Tue, 26 Jun 2001 19:47:39 +0200
User-agent: Mutt/1.2.5i

On Tue, Jun 26, 2001 at 12:36:04PM -0500, Rob Browning wrote:
: "Lars J. Aas" <address@hidden> writes:
: > Try making your own wrapper around printf() and see.  You can't -
: > you can only pretend you wrap printf() but actually forward the
: > invokation to vprintf().  That's probably why the vprintf() family
: > is there - so you can make your own variants that wrap the real
: > printf-implementation.  It's a moot point since it's only a problem
: > if you need to make wrapper functions, and you may not want to
: > invest any extra effort in libguile to support that.
: 
: Actually this is a good point.  The problem is that there's no
: portable (AFAIK) implementation of anything like "apply" for C given a
: varargs list.  You can't build an argument list and then call a normal
: varargs C function using that list.

That's true - you can not build the va_list yourself (without butting your
head up against the portability wall), but you can forward va_list objects,
and you can forward va_list objects after having read in (and thereby
discarding) the first N arguments.

  Lars J
-- 
"Imagine, the task force guy says, telling a passenger on arrival that a dildo
kept her baggage on the East Coast.  Sometimes, it's even a man.  It's airline
policy not to imply ownership in the event of a dildo.  Use the indefinite
article.  A dildo.  Never your dildo.  Never, ever say the dildo accidentally
turned itself on.  A dildo activated itself and created an emergency situation
that required evacuating your baggage."



reply via email to

[Prev in Thread] Current Thread [Next in Thread]