[ibis-macro] Re: Parameter passing idea
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
- Date: Mon, 20 Aug 2007 15:52:13 -0700
Ambrish,
I am not sure if requiring the parameter file name to be the
same as the executable file name is a good idea, because I
can see situations when the same executable file may be
used with different sets of parameters. But we could
eliminate the second subparameter by putting the parameter
file name after the executable file name separated by at
least one white space. This syntax would also match the
external model/circuit corner subparameter syntax where
the entity(architecture) or module name follows the .vhd
or .va file names. This is what that would look like:
[Algorithmic Model]
Executable Windows_VisualStudio_32 example_rx.dll
ParameterFileName.ami
This would allow each executable to have its own independent
parameter file association.
Arpad
============================================================
-----Original Message-----
From: Ambrish Varma [mailto:ambrishv@xxxxxxxxxxx]
Sent: Monday, August 20, 2007 3:44 PM
To: Muranyi, Arpad; IBIS-ATM
Subject: RE: [ibis-macro] Re: Parameter passing idea
Hi Arpad,
This is how we had originally proposed the change. We can also eliminate
the 'Parameter_file_name' subparameter by simply requiring to have the
parameter file name to be the same as the dll name (in this case, it
will be example_rx.ami).
The only scenario where keeping the subparameter would be useful is when
there might be multiple parameter files for a single dll.
Whatever we chose - I think we are on the right path here.
-Ambrish
---------------------------------------------------------------------
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:
