Calling functions whose signature/arguments are only known at runtime

[Peter Lobsinger]

On Wed, Mar 17, 2010 at 10:23 AM, Andrew Whitworth
<wknight8111 at gmail.com> wrote:
> Parrot_ext_call and Parrot_pcc_invoke_from_sig_object don't exactly do
> the same things. Parrot_ext_call is specifically designed to work from
> C and take arguments as C datatypes. Plus, it gives us a convenient
> place to add context entry and exit code, thread synchronization code,
> or GC management code (turn off GC, such as a concurrent GC, when we
> exit managed code), etc. I don't think we do any of these things yet,
> but I can imagine many reasons why we will want to.

In that case, a similar argument can be made for an interface that
uses a void *[] or callbacks. Works from C, takes C datatypes, gives a
logical place to transition between managed/unmanaged code.