Hi,
I realize this is very late, but the following issues are
all minor and most of them are editorial in nature so hopefully
there will still be time to get them in. Note, all page
references are document pages, *not* PDF pages.
P. ii, the third section from the bottom: The document version is
shown here as 1.1.0 but as 1.0.1 in the rest of the document.
Section 5.2.2.2, p. 26, second paragraph: The first two sentences
which define when input-ready propagation happens should occur after
the definition of the term `input-ready propagation'.
Section 5.2.5.2, p. 35-36: The notes under CclockEnabled and
CclockNegEdgeEnabled are actually part of the specification and should
thus not be notes.
Section 5.2.5.3, p. 36-37: Should this whole section be a note?
Section 5.4.2.2, p. 41, paragraph below function prototypes: Why do we
state that the info callback must not be used to abort the simulation?
We cannot prevent the user from doing this and it will certainly not
lead to incorrect results up to the point of the abort. Perhaps the
intent of this sentence is to say that info messages may occur at any
time even during a perfectly normal run, so that aborting the
simulation would be premature. But explicitly forbidding aborting
the simulation seems silly as it cannot be enforced anyway.
Section 5.4.7.2, p. 57, line 4, last sentence: Remove the first word
`by'.
Thanks,
Per
-- Per Bojsen Email: <bojsen@zaiqtech.com> Zaiq Technologies, Inc. WWW: http://www.zaiqtech.com 78 Dragon Ct. Tel: 781 721 8229 Woburn, MA 01801 Fax: 781 932 7488Received on Thu Jan 13 07:16:31 2005
This archive was generated by hypermail 2.1.8 : Thu Jan 13 2005 - 07:17:43 PST