All,
Currently IBIS says:
3. To facilitate portability between operating systems, file names used
in a .ibs file must only have lower case characters. File names should
have a basename of no more than forty (40) characters followed by a period
("."), followed by a file name extension of no more than three characters.
The file name and extension must use characters from the set (space, " ",
0x20 is not included):
a b c d e f g h i j k l m n o p q r s t u v w x y z
0 1 2 3 4 5 6 7 8 9 _ ^ $ ~ ! # % & - { } ) ( @ ' `
The file name and extension are recommended to be lower case on systems
that support such names.
I would like to submit a BIRD that changes this to:
3. File names should be no more than forty (80) characters. The file
name must use characters from the following set(space, " ", 0x20 is not
included):
a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9 _ ^ $ ~ ! # % & - { } ) ( @ ' ` . /
Note that files names in the Windows operating system are case insensitive
and case preserving, while file names in Linux operating systems are case
sensitive. File names in IBIS files should be case sensitive so that the
IBIS file and the files it references will work properly on both Windows
and Linux operating systems. The "/" character is used to delineate
folders in a file name. The character sequences "./", "/.", ".." and "//"
are not permitted. the first or last character of a file name may not be
"/" or ".". The "/" character may be converted to "\" when referencing
files on Windows operating systems.
Note that this relaxes almost all rules on file names. The space character
remains an illegal file name character. When an IBIS file is delivered all
supporting files must either be in the same directory as the IBIS file, or
in a folders below this directory. Absolute files names (e.g. that begin
with // or C:) are not permitted. One reason for allowing paths in IBIS
file names is that IBIS AMI modeling, and Interconnect Modeling may result
in a large number of supporting files. Users and EDA tools may choose to
move these supporting files into other directories, and these files may be
put on a tool specific search path or adding symbolic links to file names.
The IBIS parser should have the option to report such non-standard file
names as either errors, warnings or allowed.
Any comments?
Walter
Walter Katz
<mailto:wkatz@xxxxxxxxxx> wkatz@xxxxxxxxxx
Phone 303.449-2308
Mobile 303.335-6156
