Subject: Re: Comments on P1364.1/Draft 2.3, Clause 5
From: Shalom.Bresticker@motorola.com
Date: Fri Oct 04 2002 - 02:16:59 PDT
5.6, "An asynchronous ROM shall be modeled as combinational logic
...": Better and more consistent is "by" instead of "as".
5.6, NOTE 1: "may opt to implement either as" - to implement what? The object of
the verb is missing. Also "may opt to implement" is better written simply as
"may implement".
5.6, NOTE 3: "mismatch at time 0": TECHNICAL COMMENT: I believe that at least in
some cases in some simulators, a mismatch may occur even after time 0 until the
first time the address receives a value after time 0, triggering the @*.
5.6.1, para. 2, line 3: "effect" should be "affect".
5.6.1, Example 24: line 4 should be "input wire [2:0] a);",
with right parenthesis after a.
5.6.2, para. 1: Delete "decorated with the attribute rom_block". It duplicates
previous phrase.
5.6.2, para. 1, line 2: "shall be used" should be "may be used".
5.6.2, para. 1: This paragraph says, "attributed as a rom_block". Para. 4 says,
"either of the attributes logic_block or rom_block". Confusing.
5.6.2, para. 2: Delete "In addition". In addition to what?
5.6.2, para. 2, line 3: "for", "if", "case" should be bold.
5.6.2, para. 3: Change "shall be read only" to "shall only be read".
5.6.2, para. 4: Change "attribute s" to "attributes".
5.6.3, Example 26: Delete underscores in data file. They serve no purpose, are
distracting, and placed illogically.
5.7, Note 2: "may opt to implement either as" - to implement what? The object of
the verb is missing. Also "may opt to implement" is better written simply as
"may implement".
This archive was generated by hypermail 2b28 : Fri Oct 04 2002 - 02:32:57 PDT