Walter,
Happy New Year!
I think we need to correct all areas in the Specification where the
statements and intent from Version 2.0 through 6.1 really did mean the same
directory. In the attached update, I have located areas where clarification
corrections can be made. This is very easy.
"file name" means two things: (1) self-referential, as used in the [File
Name] keyword, (2) reference to a file in the same directory or by path, as
used in much of the proposed syntax extension.
The self-referential application can make reference to the [File Name]
keyword, which also points to the Section 3(3) rules, but prohibits paths.
The other major editorial correction is to clean up "extension" in the
Specification and also in the proposed Section 3(3) revision.
We can discuss this and other suggestions at some appropriate time.
Bob
From: ibis-bounce@xxxxxxxxxxxxx [mailto:ibis-bounce@xxxxxxxxxxxxx] On Behalf
Of Walter Katz
Sent: Wednesday, December 21, 2016 2:44 PM
To: Bob Ross; ibis@xxxxxxxxxxxxx; IBIS-ATM
Subject: [ibis] Re: [ibis-macro] BIRD186 Comments
Bob,
All we need to do is say in the new "Section 3, "GENERAL SYNTAX RULES AND
GUIDELINES" that ""same directory" means that the path of the file is
reative (and below) the directory that the IBIS file is in.
Walter
From: Bob Ross [mailto:bob@xxxxxxxxxxxxxxxxx] ;
Sent: Wednesday, December 21, 2016 4:44 PM
To: wkatz@xxxxxxxxxx; ibis@xxxxxxxxxxxxx; 'IBIS-ATM'
<ibis-macro@xxxxxxxxxxxxx>
Subject: RE: [ibis] Re: [ibis-macro] BIRD186 Comments
Walter,
Thank you for pointing out more "same directory" rules than I had noted.
All statements that are in explicit conflict with Section 3(3) must be
fixed.
I can provide a set of fixes on a group-by-group or case-by-case basis and
revise my comments - including correcting some mistakes I made. This is not
a big task since one change can apply to several repeated paragraphs or
statements.
In some cases the whole sentence can be deleted. In other cases, just the
"same directory" qualifier can be removed.
For example, under the parameter Supporting_Files, the sentence below should
be deleted as part of BIRD186:
(The AMI executable models and the AMI parameter definition files are all
required to be in the same directory as the .ibs file in which they are
declared).
We could consider, but I would hold off making other changes to
Supporting_Files at this time. Many of its statements become redundant with
the proposed Section 3(3)..
As noted, there is no change in the same directory requirement for the
location of .pkg files
There would be no change in another reference to Section 3 regarding
polarity conventions.
---------
IBIS is file-based, and some files have reserved extensions. The [File
Name] keyword references Section 3(3) but contains the added rule that "/"
is not allowed. So, when we are describing an embedded [File Name] in a
file, it makes sense to just refer to the [File Name] rules.
When we make reference to a file or list it in a column for file names, the
file name now can include the relative path according the Section 3(3)
rules.
We can discuss other suggestions at an ATM meeting or Open Forum Meeting. I
will produce a new comment/suggestion document.
Bob
From: <mailto:ibis-bounce@xxxxxxxxxxxxx> ibis-bounce@xxxxxxxxxxxxx [
<mailto:ibis-bounce@xxxxxxxxxxxxx> mailto:ibis-bounce@xxxxxxxxxxxxx] On
Behalf Of Walter Katz
Sent: Tuesday, December 20, 2016 7:18 AM
To: <mailto:bob@xxxxxxxxxxxxxxxxx> bob@xxxxxxxxxxxxxxxxx;
<mailto:ibis@xxxxxxxxxxxxx> ibis@xxxxxxxxxxxxx; IBIS-ATM
Subject: [ibis] Re: [ibis-macro] BIRD186 Comments
Bob,
IBIS 6.1 has 10 places where the following is stated:
The files referenced must be located in the same directory as the .ibs file
containing the reference. The file names of parameter definition files must
follow the rules for file names given in Section 3, "GENERAL SYNTAX RULES
AND GUIDELINES".
Since the "rules for file names given in Section 3, "GENERAL SYNTAX RULES
AND GUIDELINES". will now allow (assuming BIRD 186) files to be in folders
below the .ibs file, then I do not see any need to change these 10 places.
If you feel there is a need to change each of these 10 places can you
propose a specific change that would be acceptable to you.
The only possible exception to this is an external .pkg file. IBIS 6.1 says:
If the matching package model is in an external .pkg file, it must be
located in the same directory as the .ibs file. The file names of .pkg files
must follow the rules for file names given in Section 3, "GENERAL SYNTAX
RULES AND GUIDELINES".
This is a special case, because IBIS does not in fact allow one to specify
"The file names of .pkg files", it just says look at all of the files with
extent .pkg in the same directory as the IBIS file. The whole concept of
looking in all of the files with extent .pkg in the directory of the IBIS
file requires an EDA tool to read in all .pkg file in the IBIS directory to
find the correct one, this is likely why .pkg files are not commonly used.
A file name may or may not have an extent. So even using the terms
"basename" and "extension" are only a convenience in modern operation
systems to associate applications with a file. IBIS requires that file names
have certain reserved extensions, but there are no other rules on basename
or extension that need to be given for any file name that is specified in an
IBIS file or its derivative files unless they file is a specific kind of
file (e.g. .ibs, .ami, .pkg, .ebd, .).
Walter
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Bob Ross
Sent: Monday, December 19, 2016 12:23 PM
To: ibis@xxxxxxxxxxxxx; IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
Subject: [ibis-macro] BIRD186 Comments
All,
Per the request, I have attached the concerns related to BIRD186 and also
provided some suggested revisions. Because of IBIS evolution based on
existing file name rules, many sections of IBIS need updating in these
areas:
Remove some conflicting hard-coded "same-directory" language in the document
Consistently use extension to mean the text after the last dot (IBIS
versions are not consistent here)
Clarify that file names including the reserved extension can contain lower
and upper case text
Suggest restoring basename and path as part of the file name definition -
useful later
Suggest adding a document naming convention statement that would, for
example define "file type .ibs", ".ibs file" or "IBS file" as the same file
Fine tune some details (files with no extension or just a "." are legal, no
"/" in extensions, including .ims as a reserved extension, etc.
Because of their interrelationships with BIRD186, the proposed changes
should be included in BIRD186.
Bob
--
Bob Ross
Teraspeed Labs
www.teraspeedlabs.com <http://www.teraspeedlabs.com/>
bob@xxxxxxxxxxxxxxxxx
Direct: 503-246-8048
Office: 971-279-5325
Attachment:
bird186_comments_2.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
