[ibis-macro] A question on the suggestion of using **msg for error conditions
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
- Date: Tue, 17 May 2011 22:35:14 -0700
Hello everyone:
I am working on updating the BIRD drafts we discussed in the
last ATM teleconference.
There was a suggestion that I should add some text in the
BIRD draft dealing with the return values that the **msg
argument should be used to explain the error conditions.
Thinking about how I should verbalize this, I noticed that
we only have a **msg argument in the AMI_Init function's
footprint. This raises more questions.
The current specification doesn't spell out who allocates
memory for **msg. We might want to spell out the rules
about that too, but I assume that the rules would be the
same as for AMI_parameters_out, i.e. the AMI model allocates
and clears the memory for it.
In addition, can we assume that all memory is cleared in
the AMI_Close function, and not at the time when the Init
function exits?
If these are true, can we assume that the memory at **msg
is available during the execution of both AMI_Init and
AMI_GetWave, therefore the model can write messages about
problems encountered during the execution of either
function?
Or is the model only supposed to use **msg during the
execution of AMI_Init?
Thanks,
Arpad
============================================================
Other related posts:
