DRAFT - CLASSIFICATION OF PARSER MESSAGES Error Error ...

feastcanadianSoftware and s/w Development

Dec 14, 2013 (3 years and 10 months ago)

77 views

DRAFT
-

CLASSIFICATION OF PARSER MESSAGES


Error

Error messages are issued if there is a documented specification violation based on a
syntax rule, a syntax argument violation, or some required combinatio
n of keywords, or
subparameters

and arguments. There can be some cases where a major violation such
as I
-
V to V
-
T table mismatch beyond 10% is deem
ed an Error, even if
this

limit

is n
ot
stated in the Specification, but matching is expected by proper extraction.

Warning

Warning messages

are issued based on expected common practice and expected
range of data values. They alert the user that something is likely to be wrong with the
ibis file. Usually there is not stated rul
e,

but agreed upon common expect
ations such as
range of values

Ca
ution

Caution messages are issued when even a Warning message can be incorrect or in the
case where generating a new Warning message would create Warnings in old models.
So far, there are only about five Caution messages related to an unstated rule that
V
meas should be between Vinh and Vinl for I/O models. There are a few devices
where receiver level shifting occurs and a Warning would be appropriate. Also, the dV
Caution test for consistency with I
-
V table data is the case where many old models
would be

flagged. The Caution test requires the

c
aution

flag.

(about 5 messages)

Note

Note messages so far are issued only when I
-
V data contains non
-
monotonic points.
There is no statement in the Specification on requiring monotonic data. But it is very
useful to know if any of the I
-
V data is non
-
monotonic, even if combined I
-
V tables with
clamp tables are monotonic. In fact some of the non
-
monotonic regions are outside the
normal simulation range and do not impact the simulation.

(about 1 or 2 message
s)

Internal Error

Internal Error messages occur mostly when there are system errors outside the scope
of the model

(such as memory allocation errors), or some un
-
trapped syntax violation
that would rarely be seen due to other checks.
Some statement should

not be there or
the parser is not able to parse the
code at a given line number fo
r unresolvable

reasons
.
(This may appear

as an Error message or possibly

an Internal Error statement???)

(About 14
0 messages)

Unused

Unused messages may be old messages that still exist, but should never be
encountered due to subsequent changes. In other words, the message and message
number still exists in a module, but it might be in an area of

dead


cod
e that never can
be
encounter
ed
, but might be retained for historical source code documentation. (6
messages)


------------------

Note over the years some messages have been promoted to a stronger level, and
others have been
demoted. The parser is set up
so the message number (avai
lable
using the

numbered

flag is retained. For some important or confusing messages, this
document should give some expanded description.

Currently for ibischk5 Version 5.1.2,
over 1200 message numbers are documented.