Dan Sugalski <[EMAIL PROTECTED]> wrote: > 1) Someone fixes the Eiffel interface generator to understand C > variadic functions.
Yep :) > 2) We provide a function and method call interface that assumes > you've already pre-filled in the registers according to parrot's > calling conventions That exists already albeit not in extend.* > 3) We build some sort of really simple call interface that takes an > array PMC with the parameters stuffed into it What's the difference WRT va_list? If the interface code can stuff things into an array, it sould as well be able to prepare a va_list. > 4) Parrot provides some sort of facility to autogenerate shim > functions based on a passed-in signature Besides the combinatorial problem that we already have in nci.c, why can't this interface function not do the call in the first place, if it has to investigate the signature anyway? leo
