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. -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Monday, August 20, 2007 3:32 PM To: IBIS-ATM Subject: [ibis-macro] Re: Parameter passing idea Something just popped to my mind. To be consistent with the usual keyword syntax in IBIS, we should probably not use the parentheses format for the argument, but the subparameter format in which the subparameter is the argument. So instead of my previous suggestion: [Algorithmic Model <modelName(ParameterFileName)>] we should probably use this syntax: [Algorithmic Model] Executable Windows_VisualStudio_32 example_rx.dll Parameter_file_name FileName.ami Any comments? Thanks, Arpad ==================================================== -----Original Message----- From: Hemant Shah [mailto:shah@xxxxxxxxxxx] Sent: Monday, August 20, 2007 12:05 PM To: Muranyi, Arpad; IBIS-ATM Subject: RE: [ibis-macro] Parameter passing idea I like this approach. It is technically equivalent to the two approaches discussed last week in the ATM meeting. This one has the additional benefit of using only one keyword *algorithmic modeling*. Hemant -----Original Message----- From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Muranyi, Arpad Sent: Friday, August 17, 2007 2:22 PM To: IBIS-ATM Subject: [ibis-macro] Parameter passing idea I was wondering about the parameter passing alternatives and thought of something that may be better than what we left off with in the last IBIS-ATM meeting. Instead of using a two-keyword approach, something like this: [Algorithmic Model <modelName>] [Model Parameter <ParameterFileName>] I thought we could perhaps do a single keyword approach in which we give the parameter file name as an argument to the algorithmic model call, something like this: [Algorithmic Model <modelName(ParameterFileName)>] The rule would be to have one (or no) argument to the ModelName() and this argument would always be a file name that holds all the parameters. Any comments? By the way, we have already done this with the IBIS Macro Library's IBIS buffer models and the accompanying Perl script which extracts the IV and Vt data from the IBIS file for them. (Ambrish, who wrote the Perl script is very familiar with this concept...) Arpad ========================================================== --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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