[ibis-macro] Re: A question on the suggestion of using **msg for error conditions
- From: "Walter Katz" <wkatz@xxxxxxxxxx>
- To: <Arpad_Muranyi@xxxxxxxxxx>, "'IBIS-ATM'" <ibis-macro@xxxxxxxxxxxxx>
- Date: Wed, 18 May 2011 07:01:55 -0400 (EDT)
Arpad,
I think you are proposing that AMI_GetWave can modify the content of the
data that **msg contains. I think this would work, as long as the length
of the string does not need to increase in size from what was initially
allocated by Init. I think a more satisficatory solution is a new reserved
parameter Message:
(Message (Usage Out) (Type String) (Value " ")
(Description "Message may be returned by either
AMI_Init or AMI_GetWave.
The contents of the Message string may
contain the following
keywords: **Error**, **Warning**, and
any other useful descriptive
strings that the User can interpret. The
Simulator should report
the value of Message to the User. The
EDA Tool may also make
choose to termination simulations if the
Message string contains
**Error**.
Walter
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad
Sent: Wednesday, May 18, 2011 1:35 AM
To: IBIS-ATM
Subject: [ibis-macro] A question on the suggestion of using **msg for
error conditions
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:
