[ibis-macro] Re: Question on test kits and tree parsing...
- From: Mike Steinberger <msteinb@xxxxxxxxxx>
- To: michael.mirmak@xxxxxxxxx
- Date: Wed, 11 Nov 2009 12:36:38 -0600
Michael-
"AMI compliant" DLL/EXE code requires an IBIS file, .ami file, and at
least one DLL or shared object file for each operating system supported.
That's what's in the standard and that's what we've all agreed to.
It is true that the entire contents of a .ami file is defined to be a
single parameter string which uses the parameter string syntax that we
all agreed to for input into the model itself. The .ami file, and
therefore that single parameter string is intended to be consumed by the
EDA tool; so in that sense, the answer to your question is "Yes, always".
Of course, a test kit contain a lot that goes beyond the requirements of
the standard, as enumerated above. For example, a test kit could contain
one or more example channels and/or one or more example projects. This
is entirely dependent on the EDA tool and the kit preparer.
This seems like an unusual question with a lot behind it. Have I
answered your question?
Thanks.
Mike S.
Mirmak, Michael wrote:
Does AMI formally expect tree details and other parameters to be parsed/assembled into a
single string for consumption by the EDA tool? The test kits seem to include this. Is
this a requirement for "AMI compliant" DLL/EXE code?
Thanks in advance...
- MM
---------------------------------------------------------------------
IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/
IBIS Macro reflector: //www.freelists.org/list/ibis-macro
To unsubscribe send an email:
To: ibis-macro-request@xxxxxxxxxxxxx
Subject: unsubscribe
---------------------------------------------------------------------
IBIS Macro website : http://www.eda.org/pub/ibis/macromodel_wip/
IBIS Macro reflector: //www.freelists.org/list/ibis-macro
To unsubscribe send an email:
To: ibis-macro-request@xxxxxxxxxxxxx
Subject: unsubscribe
Other related posts:
