Re: motoX_callEDF, motoX_callMDF

On Sunday, April 27, 2003, at 02:13  PM, Stefano Corsi wrote:

> Hi Dave,
>
> in motoc.c there are no simple motoX_callEDF, motoX_callMDF wrapper 
> functions
> and the function calling process is much more difficult to understand 
> (and
> use).

	This is true and it's a re-factoring exercise I've been meaning to 
take on for some time. I can try doing something with it tonight. Or, 
if you wanted to take a shot at this task, that would be cool too! One 
thing that may simplify the process is that I do not believe there is 
any real difference in calling MDFs and EDFs from generated code 
(although there may be some difference when calling constructors).

>  Do you have any suggestion for calling operator functions in compiled
> mode from inside motox_try_method_operator and 
> motox_try_function_operator?
>
	Well, the logic for determining if there is an overloaded operator 
will be the same and should thus remain factored in motox_try... The 
complexity is, as you point out, generating the code for the function 
call. I think that really does come down to factoring the code 
generation portion of motoc_fn into another functoin that can be called 
in the case of overloaded operators.

-Dave

> Stefano
>