Editor’s Note: Does the BNF reflect the
preceding restrictions? For example (if I am not mistaken) the current BNF can
have @(expression), which will allow @(a = b | c) (the
example deleted with draft 5 from section 8.11).
Note that & is
higher precedence than ^, following the Verilog standard.
Editor’s Note: Is the note above needed?
It came from the old Superlog LRM, and was intended
to show that Superlog used Verilog’s
precedence instead of C’s. The SV LRM’s purpose is to
show where SV operators fall with respect to Verilog operaotrs.
Editor’s Note: “bits” is not a keyword so
I removed the bold-courier font. A concatenation can be used with reg, wire and
many other data types. Since that is standard Verilog, I deleted the reference
to just the logic data type.
Editor’s Note: Does the BNF reflect this special case that for a
string a non-constant replication multiplier is allowed?