[ibis-macro] IBIS-AMI More on NA

From: Bob Ross <bob@xxxxxxxxxxxxx>
To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
Date: Sat, 27 Feb 2010 21:12:00 -0800
All:

It is hard to argue about a removal of NA when it appears to be a
powerful improvement:

|     Value:     <value> Single value data
|                     <value>=NA implies there is no constraint on the <value>
|                     NA is not allowed for Info, In or InOut parameters.

|     Range:     <typ> <min> <max>
|                     <typ> >= <min>
|                     <typ> <= <max>
|                     <min> = NA means there is no lower limit to a value
|                     <max> = NA means there is no upper limit to a value

|     Increment: <typ> <min> <max> <delta>
|                     <typ> >= <min>
|                     <typ> <= <max>
|                     <min> = NA means there is no lower limit to a value
|                     <max> = NA means there is no upper limit to a value

Everything seems so simple and almost cleaver, but that is very deceptive.

I may be misinterpreting "context-specfic" as something that prevents
full language BNF definition, but NA appears to be a context-specific parameter
that requires special case handling.  This becomes very costly.

So, I very strongly object to inserting NA in the official IBIS-AMI, and
request its removal everywhere to restore the 5.0 baseline definitions.
While we will always have some context-specific syntax, we should not add
more.

We can justify what it is really needed.  Then we could provide equivalent
functionality with any of these commands.

Value <value>
Value_select <value>          | User select, default given

Range <typ> <min> <max>
Range_select_max <typ> <min>  | user select max
Range_select_min <typ> <max>  | user select min
Range_select_min_max <typ>    | user select min and max

Increment <typ> <min> <max> <delta>
Increment_select_min <typ> <min> <max> <delta>
Increment_select_max <typ> <min> <max> <delta>
Increment_select_min_max <typ> <delta>

My instincts tell me that it is much better to do it this
way than to create a nearly un-maintainable context-specific
set of rules within a language.

Deleting NA will speed up all aspects of the whole process.

Bob

--
Bob Ross
Teraspeed Consulting Group LLC     Teraspeed Labs
121 North River Drive              13610 SW Harness Lane
Narragansett, RI 02882             Beaverton, OR 97008
401-284-1827                       503-430-1065
http://www.teraspeed.com           503-246-8048 Direct
bob@xxxxxxxxxxxxx

Teraspeed is a registered service mark of Teraspeed Consulting Group LLC

---------------------------------------------------------------------
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] IBIS-AMI More on NA

Other related posts:
