Chris, Bob,
Sounds like another Bird, #18? Bob, since the bulk of the Bird is
contained in the paragraph you just wrote, do you want to post it?
Will
Chris
The column headers for [Diff Pin] should be listed in the specified order.
We missed that point when writing the specification. It should be clarified
in IBIS Version 2.1. This restriction should simplify all parsers and
should not cause anyone any problems.
IBIS Ver. 2.0 specifies that the column headers for [Pin Mapping] must appear
in the listed order. The first three column headings of [Pin] must also
appear in the listed order, but the last three column headings for L_pin,
C_pin and R_pin can appear in any order as long as they are all listed.
The order of columns for all keywords which support typ-min-max columns is
fixed since no column headers are specified (the specification gives optional
comment line headings for clarity).
Bob Ross
Interconnectix, Inc.
> Hello,
> Just a point of clarification please. I'm reading the v2.0 spec.
> and find the same question I had with the v1.0 spec unanswered.
> I ASSUME that column headings must appear in the specified order.
> In other words,
> [Diff Pin] inv_pin vdiff tdelay_typ tdelay_min tdelay_max
> is the specified syntax, so
> [Diff Pin] tdelay_typ inv_pin tdelay_min vdiff tdelay_max
> or any other rearrangement is illegal. Right?
> Chris
> cer@cadence.com
Received on Wed Jul 20 14:05:31 1994
This archive was generated by hypermail 2.1.8 : Fri Jun 03 2011 - 09:52:28 PDT