[sv-bc] Editorial suggestions for Draft 3

Matt,

I converted some of my comments into numbered mini-proposals (see
below),
but ran out of time for many of the knottiest items, such as

    http://www.eda-stds.org/sv-bc/hm/5791.html

and will have to leave them for future Mantis items.


--- BP1-5-1 ---------------

In 5.8, undelete the Note.  And as described in the 03-07-07 bugnote of

   http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0000700

change "Greek letter m" to use a Greek letter mu instead of a Latin 'm',
and in "properly ms", change the Latin 'm' before 's' to a Greek mu. 


--- BP1-5-2 ----------------

In 5.5.4 replace

   "The affects of a compiler directive is limited to a compilation unit
(see 3.8.1) and shall not affect other compilation units."

with

   "The effects of a compiler directive are limited to a compilation
unit
(see 3.8.1) and shall not affect other compilation units."


--- BP1-5-3 ----------------

In 5.9, in "A string literal can be assigned to an integral type",
replace "type" with "data object".


--- BP1-5-4 ----------------

In 5.9, REPLACE

   "The rules of SystemVerilog assignments shall be followed if the
packed
    array width is does not match the number of characters multiplied by
8."

WITH

   "The rules of SystemVerilog assignments shall be followed if the size
   of the data object is not the number of characters multiplied by 8."

 
--- BP1-5-5 ----------------

In 5.9, in "When integral type is larger than required",
replace "integral type" with "the integral data object".



--- BP1-5-6 ----------------

In 5.9, replace ".padded" with "padded".



--- BP1-5-7 ----------------

In 5.9, in "larger than the destination integral type",
replace "type" with "data object".
  


--- BP1-5-8 ----------------

In 5.9, replace

     "String literals stored in vectors" 

with

     "String literals stored in integral data objects"


--- BP1-6-1 ----------------

In 6.6.1, remove the italics from "the" in "the msb" and from
"specified by the" in "specified by the lsb".


--- BP1-6-2 ----------------

After Table 6-8, remove

    "Note-The 1364-2005 standard only had the reg, integer and time
     integer variables."


--- BP1-6-3 ----------------

In 6.10, replace

     "These three types are collectively referred to as real variables."

with

     "Variables of these three types are collectively referred to as
real variables."
    

--- BP1-6-4 ----------------

In 6.13, in

     "A class variable is a dynamic data type that
     can hold a handle to a class object. "

remove

     "is a dynamic data type that"


--- BP1-6-5 ----------------

As explained in

    http://www.eda-stds.org/svdb/bug_view_page.php?bug_id=0000507

In 6.18.3, change "non local" to "nonlocal".


--- BP1-6-6 ----------------

In 6.20.2, remove the editorial question about the Note, which is
correctly only a note because there is already normative text saying

   "If all data types within a packed structure are 2-state,
the structure as a whole is treated as a 2-state vector. If any data
type within a packed structure is 4-state, the structure as a whole is
treated as a 4-state vector. If there are also 2-state members in the
structure, there is an implicit conversion from 4-state to 2-state when
reading those members and from 2-state to 4-state when writing them."


--- BP1-7-1 ----------------

In 7.2.4, replace

    "Each packed dimension in the array is known as a memory element
or word"

With

    "An element of the fastest-varying unpacked dimension in the
array is known as a memory element or word"


--- BP1-7-2 ----------------

In 7.2.1, in "A vector (see 6.6) is a a one-dimensional packed array",
change "a a" to "a".


--- BP1-7-3 ----------------

In Table 7-2, remove the "in" in "replication in".
 

--- BP1-7-4 ----------------

In 7.1.1, because of the issues in 

   http://www.eda-stds.org/sv-bc/hm/5780.html 

remove 

   "A structure represents a collection of variable types that can
    be referenced using the structure name. By default, structures are
    unpacked, meaning that there is no defined representation on how
    each variable in the collection is stored.  Unpacked structures
    can contain any variable data type."


--- BP1-8-1 ----------------

In 8.1, in "Class instances, or objects, can be passed around via object
handles, which provide a safe-pointer capability in the language" remove
"in the language".
 

--- BP1-9-1 ----------------

In 9.1, replace

  "The initial procedure shall execute only once, and its activity
   shall cease when the statement has finished. In contrast, the
   always procedures shall execute repeatedly. Its activity shall
   cease only when the simulation is terminated."

with

  "An initial procedure shall execute only once, and its activity
   shall cease when the statement has finished. In contrast, an always
   procedure shall execute repeatedly, and its activity shall cease
   only when the simulation is terminated."


--- BP1-9-2 ----------------

In 9.1.3, in "All final procedure shall execute in an arbitrary order"
replace "procedure" with "procedures".


--- BP1-9-3 ----------------

In 9.2, in "The procedural statements in sequential block shall be
executed sequentially in the given order" replace "in sequential"
with "in a sequential".


--- BP1-9-4 ----------------

In 9.2, in "The procedural statements in parallel block shall be
executed concurrently" replace "in parallel" with "in a parallel".


-- BP1-10-1 ----------------

In 10.2.2, in "or module output,." remove the comma.


-- BP1-10-2 ----------------

In 10.3, replace 

      "variable type on left-hand side"

with 

      "variable type on the left-hand side"


-- BP1-10-3 ----------------

In 10.4, remove the sentence

   "Variable declaration assignments are only allowed
    at the module level."


-- BP1-11-1 ----------------

In Table 11-1, remove "C-like".


-- BP1-12-1 ----------------

In 12.2, remove the sentence

   "Pessimism reduction can also be done using unique-case priority-case
(see 12.3.3)."


-- BP1-12-2----------------

In 12.5.1, in "The variable used to control a for-loop can be declared
prior to the loop", replace "variable" with "variables".


-- BP1-12-3 ---------------

In 12.5.1, in "The variable used to control a for-loop can also be
declared within the for-loop", replace "variable" with "variables".


-- BP1-12-4 ----------------

In 12.5.1, in "The variable used to control a for-loop can also be
declared within the for-loop", replace the second "for-loop" with
"loop".


-- BP1-12-5 ----------------

In 12.7, replace "can have name specified" with "can have a name
specified".


-- BP1-13-1 ----------------

In 13.1, remove the sentence

   "A function shall have at least one input type argument"

and remove the editorial question in the margin.


-- BP1-13-2 ----------------

In 13.1, in "A function nonvoid function" remove the first "function".


-- BP1-13-3 ----------------

In 13.3, replace 

   "A function declaration can include an optional function_data_type
   or packed_dimension range, which shall specify the type or size
   of value returned by the function. A function specified without a
   function_data_type or packed_dimension defaults to a scalar logic
   for the return value. If a packed_dimension is specified, the
   function shall return a packed array of type logic."

with

   "To indicate the return type of a function, its declaration can
either include
    an explicit function_data_type or use an implicit syntax that
indicates
    only the ranges of the packed dimensions and, optionally, the
signedness.
    When the implicit syntax is used, the return type is the same as if
the
    implict syntax had been immediately preceded by the logic keyword."


-- BP1-13-4 ----------------

In 13.3.3, in "These items shall be shared across all uses of the task
executing concurrently" replace "task" with "function".


-- BP1-13-5 ----------------

In 13.3.3, in "Functions can defined to use static storage by explicitly
defining
the task as static" replace "can defined" with "can be defined" and
replace "task"
with "function".


-- BP1-13-6 ----------------

In 13.4, replace "listed of the call" with "listed in the call".
 
       
-- BP1-13-7 ----------------

In 13.4.4, in "The fun function", the "fun" should be in a monospaced
font.


-- BP1-22-1 ----------------

In 22, in "The formal syntax for a module definitions", replace
"definitions"
with "definition".


-- BP1-22-2 ----------------

In 22.1, in "or and entire complex digital system", replace "and"
with "an".


-- BP1-22-3 ----------------

In 22.2, replace 

    "A module can be used (instantiated) in two ways"

with

    "A module can be instantiated in two ways"


-- BP1-22-4 ----------------

In 22.2.2, in "is used illustrate", replaced "used" with "used to".


-- BP1-22-5 ----------------

In 22.2.2.2, replace

   "The following example instantiations of a module call A is illegal"

with 

   "The following example instantiations are illegal"
 

--- BP1-A-1 ----------------

Fix the BNF according to the proposal in  

    http://www.eda-stds.org/sv-bc/hm/5779.html



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.