[ibis-macro] Re: Out InOut Info BIRD nested parameters

  • From: Walter Katz <wkatz@xxxxxxxxxx>
  • To: <mlabonte@xxxxxxxxxx>, "Arpad Muranyi" <Arpad_Muranyi@xxxxxxxxxx>
  • Date: Tue, 29 Sep 2015 16:36:34 -0400 (EDT)

Mike,



No need to be so complicated:



(SpecialParameters (Usage Info) (Type String)
(Table
("AnalogModel(TStoneFile")
)
)



Since in "'s ('s are allowed.



Walter



From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Mike LaBonte
Sent: Tuesday, September 29, 2015 2:26 PM
To: Arpad Muranyi
Cc: ibis-macro@xxxxxxxxxxxxx
Subject: [ibis-macro] Out InOut Info BIRD nested parameters



Hi Arpad,



A followup to the IBIS-ATM call today: the Model_Specific parameters that
we want to list in SpecialParameters could possibly be nested under
intermediate branches. For example:



(Model_Specific

(AnalogModel

(TStoneFile (Usage Info) (Type String) (Value "something.s4p")

(Description "Broadband on-die model"))

)

)



How should that be represented in SpecialParameters? A few ideas:



1. Use spaces to delimit hierarchical elements, since parameter names
cannot contain spaces:
(SpecialParameters (Usage Info) (Type String)
(Table
("AnalogModel TStoneFile")
)
)

2. Use table columns:
(SpecialParameters (Usage Info) (Type String String)
(Table
("AnalogModel" "TStoneFile")
)
)

3. Only top level can be specified, everything under it is special:
(SpecialParameters (Usage Info) (Type String)
(Table
("AnalogModel")
)
)



There may be other ways .



Mike

Other related posts: