Draft 4: Sections 12.1, 12.3.6

From: Shalom Bresticker (shalom@msil.sps.mot.com)
Date: Sun Jan 09 2000 - 06:53:37 PST

<x-html>
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
1. In the middle of the 2nd paragraph of 12.1 (p. 163):
<p>"The order used used in defining the list of parameters in the <tt>module_parameter_port_list</tt>
and in the list of ports can be significant when instantiating the module
(see 12.1.2)."
<p>The use of "<tt>module_parameter_port_list</tt>" and "list of ports"
should be parallel and consistent.
<br>That is, if "<tt>module_parameter_port_list</tt>" is the BNF term
(Courier font, with underscores),
<br>then "list of ports" should also be "<tt>list_of_ports</tt>", as in
Syntax 12-1.
<p>Actually, for true consistency, "<tt>list_of_ports</tt>" should be "<tt>module_port_list</tt>"
to be parallel to "<tt>module_parameter_port_list</tt>".
<p>2. The 1st paragraph of 12.3.6 (Connecting module instance ports by
name), p. 186, got messed up.
<br>Stefen's proposal, in HTML, contained both additions and crossouts,
but the crossouts were not done, maybe because you don't see the crossouts
when you print the mail.
<p>Anyway, it should be:
<p> " The second way to connect module ports consists of explicitly
linking the port definition name
<br> from the module declaration to the expression used in
the instantiating
<br> module. This compound name is then placed in the list
of module connections. The name of port
<br> shall be the name specified in the module definition.
The name of port cannot be a bit-select, a
<br> part-select, or a concatenation of ports. If the module
port definition was implicit, the
<br> port_expression must be a simple port_identifer which
is used as name of port. If the module port
<br> definition was explicit, the explicit name is used as
the name of port.
<p> The port expression can be any valid expression using identifiers
in the scope of the instantiating
<br> module."
<p>Note that the list of 4 types of port expressions at the top of p. 187
is deleted.
<p>But there is still no reason that hierarchial identifiers should not
be allowed.
<br>Any expression which is valid to use in the instantiating module should
be allowed.
<p>Shalom
<pre>--

************************************************************************
Shalom Bresticker email: shalom@msil.sps.mot.com
Motorola Semiconductor Israel, Ltd. Tel #: +972 9 9522268
P.O.B. 2208, Herzlia 46120, ISRAEL Fax #: +972 9 9522444
<A HREF="http://www.motorola-semi.co.il/"><a href="http://www.motorola-semi.co.il/">http://www.motorola-semi.co.il/>>
************************************************************************</pre>
 </html>

</x-html>

This archive was generated by hypermail 2.1.4 : Mon Jul 08 2002 - 12:54:10 PDT and
sponsored by Boyd Technology, Inc.