…ot_api_pmc_new_call_object and Parrot_api_pmc_setup_signature
…for constructing a CallContext from a signature string and a variadic argument list. brrt++ for the suggestion
…call_object. Use that in the new_call_context op. Also, expose it through a convenient new Parrot_api_new_call_object API function. brrt++ for the suggestion
at the start of the declaration. For #770. But note: As of this commit the test reports 3 failures which, in fact, are not impeding Parrot's build with g++.
…tances in make test
…hese directives in coretest
…ser. These mechanisms are to be replaced by the newer and more flexible .annotate directive.
… use of Parrot_pcc_get_*_reg functions. These functions are marked PARROT_EXPORT, and they probably need to be for things like dynops. However, we should definitely provide some warnings/guidance in case somebody wants to try to use these functions for other purposes.
To my knowledge this function has never 'walked up the scopes', and I'm not aware of any problems caused by that omission. Further, a request for a test or use-case over a year ago went unanswered, suggesting there isn't any user desire for such a change. This commit closes #563