--- Begin Message ---
- From: "wkatz@xxxxxxxxxx" <wkatz@xxxxxxxxxx>
- To: ckumar <ckumar@xxxxxxxxxxx>
- Date: Thu, 30 Sep 2010 13:41:27 -0700
Kumar,
From pages 186/187 of IBIS 5.0
| The syntax for this string is:
|
| 1. Neither names nor individual values can contain white space characters.
| 2. Parameter name/value pairs are always enclosed in parentheses, with the
| value separated from the name by white space.
| 3. A parameter value in a name/value pair can be either a single value or a
| list of values separated by whitespace.
| 4. Parameter name/value pairs can be grouped together into parameter groups
| by starting with an open parenthesis followed by the group name followed
| by the concatenation of one or more name/value pairs followed by a close
| parenthesis.
| 5. Parameter name/values pairs and parameter groups can be freely
| intermixed inside a parameter group.
| 6. The top level parameter string must be a parameter group.
| 7. White space is ignored, except as a delimiter between the parameter name
| and value.
| 8. Parameter values can be expressed either as a string literal, decimal
| number or in the standard ANCI 'C' notation for floating point numbers
| (e.g., 2.0e-9). String literal values are delimited using a double
| quote (") and no double quotes are allowed inside the string literals.
| 9. A parameter can be assigned an array of values by enclosing the
| parameter name and the array of values inside a single set of
| parentheses, with the parameter name and the individual values all
| separated by white space.
Note 2. above:
| 2. Parameter name/value pairs are always enclosed in parentheses, with the
| value separated from the name by white space.
The following (from Ambrish and Ken) follow this rule:
(abc 10.1 20.2 30.3 )
The following example that you propose for multi-row tables violates this rule:
(name (a11 a12 a13) (b11 b12 b13))
Walter
Walter Katz
303.449-2308
Mobile 303.883-2120
wkatz@xxxxxxxxxx
www.sisoft.com
-----Original Message-----
From: ckumar [mailto:ckumar@xxxxxxxxxxx]
Sent: Thursday, September 30, 2010 2:26 PM
To: wkatz@xxxxxxxxxx
Cc: kwillis@xxxxxxxxxxx; IBIS-ATM
Subject: Re: [ibis-macro] Re: Table usage
a single row table can be passed as
(name a11 a12 a13)
multi rows
(name (a11 a12 a13) (b11 b12 b13))
On Thu, 30 Sep 2010 12:31:37 -0400, "Walter Katz" <wkatz@xxxxxxxxxx>
wrote:
> Ken,
>
> A Table, by definition, supports multiple rows. How would you pass the
> following?
>
> (abc (Usage In) (Type Float) (Format Table (10.1 20.2 30.3) (1. 2. 3.)
(4.
> 5. 6.)) (Description "Table example"))
>
> It is this case that makes Format Table as a Usage In, InOut or Out
> parameter problematic, and not defined, or allowed in the IBIS 5.0
> definition of the AMI_parameters_in or AMI_parameters_out string
> definition.
>
>
> We need to pass similar types of data into the DLL's that we write; we
> chose
> to do this in the following manner:
>
> (abc (Usage In) (Type String) (Format Value "10.1 20.2 30.3")
(Description
> "Alternative example"))
>
> Here is what it looks like when being passed to the DLL:
>
> (abc "10.1 20.2 30.3")
>
>
> Your method satisfies all of the rules defined in pages 186 and 187, as
> long
> as the Table only contains one row.
>
> I think there are the following options:
>
> 1. Allow a Format Table to have Usage In (or InOut, or Out), but require
> that such a Table have only one Row.
> 2. Require that Format Table has (Usage Info)
>
> Option 1 requires some work by all of the other EDA vendors, and a
> clarification to the definition of Format Table.
> Option 2 requires some work by Sigrity, and a clarification to the
> definition of Format Table.
>
> Does anyone have any other (preferably better) ideas?
>
> Walter
>
> Walter Katz
> 303.449-2308
> Mobile 303.883-2120
> wkatz@xxxxxxxxxx
> www.sisoft.com
>
> -----Original Message-----
> From: ibis-macro-bounce@xxxxxxxxxxxxx
> [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]On Behalf Of Ken Willis
> Sent: Thursday, September 30, 2010 11:50 AM
> To: IBIS-ATM
> Subject: [ibis-macro] Table usage
>
> Hi,
>
> Following up from the last call, here is an example of Table being used
in
> an AMI file:
>
> (abc (Usage In) (Type Float) (Format Table (10.1 20.2 30.3))
(Description
> "Table example"))
>
> Here is what it looks like when being passed to the DLL:
>
> (abc 10.1 20.2 30.3 )
>
> Thanks,
>
> Ken Willis
> Sigrity, Inc.
> 860-871-7070
> kwillis@xxxxxxxxxxx <mailto:kwillis@xxxxxxxxxxx>
---------------------------------------------------------------------
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
--- End Message ---
