Nick Glencross wrote:
Hmmm. still don't think that's what I want. Obviously this is in the
context of the NCI callback stuff that I'm looking into -- no surprises
there.
Ah callbacks again. As these are called by C code, you really should not
a function signature at compile-time.
In case 2
Leopold Toetsch wrote:
On Oct 30, 2005, at 1:54, Nick Glencross wrote:
Quick question...
I've been looking through inter_run and extend to see how to pass
arguments to a parrot method/function from C, but all the prototypes
that I've seen have '...' or 'va_list' to accept the arguments.
On Oct 30, 2005, at 1:54, Nick Glencross wrote:
Quick question...
I've been looking through inter_run and extend to see how to pass
arguments to a parrot method/function from C, but all the prototypes
that I've seen have '...' or 'va_list' to accept the arguments.
If I don't know what the
Quick question...
I've been looking through inter_run and extend to see how to pass
arguments to a parrot method/function from C, but all the prototypes
that I've seen have '...' or 'va_list' to accept the arguments.
If I don't know what the arguments or their respective types are at
compile
