Re: Parser, Case, Resolution

Text item:

Kellee,

Very good, I agree with the recommendation you and Bob came up with. In fact I
thought I recommended the same thing in one of my EMAILs last week. I might not
have stated it clearly enough, because I didn't get any responses to it.

Another way of looking at this issue is that no other error message stops the
parser from running. Why should this do that? Just give a message and keep
running.

However, I have a minor thing to pick on.

I would issue an ERROR message and not just a warning, since it is a direct
violation of the spec. To be forgiving to case-insensitive systems, I would put
a statement in the error message that tells the user something like this:

"IBIS file names must be all lower case. Please ignore this message if you are
running in an operating system which does not allow case-sensitive file names."

Of course, the parser would continue parsing which it currently does in the case
of all other error messages.

Arpad Muranyi
Intel Corporation
______________________________ Reply Separator _________________________________
Subject: Parser, Case, Resolution
Author: kellee@nwlink.com at Internet_Gateway
Date: 3/8/95 12:45 PM

From: Kellee Crisafulli, HyperLynx

Greetings,

  Bob Ross and I had a long conversation today about the case sensitivity
issue with the
parser and file names. Bob was initially against allowing upper case file
names from the
operating system to pass through the parser. The final out come of our
conversation was
the following:

  1) The file name must remain lower case in the file itself (per the
specification).
  2) Either upper, lower or mixed upper/lower file names should be accepted
on the
     command line.
  3) If the file name from the command line is not all lower case than the
parser must
     post a WARNING (accept versions compiled for DOS). The warning should
be state that
     the file name should be lower case.
  4) The comparision of the command line file name to the file name in the
IBIS file must
     be case INSENSITIVE.
  4) The file should be parsed and checked no matter what the case. For
example if the
     user types in a lower case name and the file name on the system is
upper case because
     it came from a DOS enviorment the file should still be parsed. If
there are
     multiple file names x1.ibs, X1.IBS, x1.IBS, x1.Ibs then the file name
which matches
     exactly what the user typed should be checked if present. If not then
it is suffient
     to check only for a lower case name.

Is this acceptable to everyone?

Have a great day...Kellee Crisafulli, HyperLynx Inc.

Text item: External Message Header

The following mail header is for administrative use
and may be ignored unless there are problems.

***IF THERE ARE PROBLEMS SAVE THESE HEADERS***.

Subject: Parser, Case, Resolution
From: kellee@nwlink.com
To: ibis@vhdl.org
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0
X-Mailer: Windows Eudora Version 2.0.3
Message-Id: <199503082040.AA08916@washington.nwlink.com>
Date: Wed, 8 Mar 1995 12:40:58 -0800
Received: by washington.nwlink.com id AA08916
  (5.67b/IDA-1.5 for ibis@vhdl.org); Wed, 8 Mar 1995 12:40:58 -0800
Received: from washington.nwlink.com (nwlink.com) by vhdl.vhdl.org (4.1/SMI-4.1/
BARRNet)
     id AA06456; Wed, 8 Mar 95 12:46:58 PST
Received: from vhdl.vhdl.org by hermes.intel.com (5.65/10.0i); Wed, 8 Mar 95 12:
45:50 -0800
Received: from hermes.intel.com by relay.jf.intel.com with smtp
     (Smail3.1.28.1 #2) id m0rmScB-000twpC; Wed, 8 Mar 95 12:45 PST
Received on Thu Mar 9 13:00:44 1995