[ibis-macro] Re: About the Typos BIRD comments from Fangyi

  • From: Mike Steinberger <msteinb@xxxxxxxxxx>
  • To: ibis-macro@xxxxxxxxxxxxx
  • Date: Tue, 07 Dec 2010 11:03:03 -0600

On 12/07/2010 10:56 AM, Muranyi, Arpad wrote:

With regards to the "obvious" on how the parameter types

In, Out, and InOut are passed in and out of the DLL, I

need to restate a question I asked once before:

If we establish the rule that In and InOut is passed into

the DLL through the AMI_parameters_in argument, and Out

and InOut are returned by the DLL through the AMI_parameters_out

argument, how are we going to deal with the situation when the

Init function contains an optimizer and returns the optimized

parameters (tap coefficients, for example) though the

AMI_parameters_out argument?  Remember, the GetWave function

does NOT have an AMI_parameters_in argument.  How is the

Init function going to pass the optimized parameters to

GetWave?

Ummm... How 'bout if the memory pointed to by AMI_memory_handle included memory for the optimized tap values? Isn't that the sort of thing we put AMI_memory_handle there for in the first place?

Initially I thought that the AMI_parameters_in argument is

visible to GetWave also, and it could see the optimized

parameters in that argument.  But this discussions seems to

indicate that the Init function is not returning the optimized

parameters in the AMI_parameters_in argument, on in the

AMI_parameters_out argument which is not visible to GetWave,

as far as I can tell...  Am I missing something "obvious"?

Any suggestions?

Thanks,

Arpad

================================================================



Other related posts: