RE: [sv-bc] e-mail ballot: respond by Dec 3, 8am PST

Stu, 

Your proposal says things like --

  "Declarations such as typedefs and constants declared in packages can
be referenced in module, interface or program port declarations by
importing the package as part of the module, interface or program
declaration."

  "Syntax 25-4-Package import in module, interface, or program
declaration syntax"

  "Declarations that are imported as part of a module, interface or
program declaration are visible throughout the module, interface or
program. These imported package items can be used in parameter and port
declarations."


I don't understand that at all.  Are these intending to talk about
package imports statements in the HEADERS of module, interface and
program declarations?  Surely the following package import statement is
part of the module declaration!

   module m;
     import pkg::*;
   endmodule

Less importantly, what does it mean to import a declaration?  An import
declaration doesn't import a declaration, it imports a symbol that has
been declared in the package.

-- Brad

-----Original Message-----
From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of
Stuart Sutherland
Sent: Thursday, November 29, 2007 8:56 PM
To: sv-bc@eda.org
Subject: RE: [sv-bc] e-mail ballot: respond by Dec 3, 8am PST


Shalom has pointed out that in the proposal for Mantis 329, it is not
necessary to have a footnote for non-ANSI headers, since this type of
header must always have a port list (the purpose of the footnote is to
avoid a package import in the module header that is not followed by
either a parameter list or a port list).  Shalom also suggested adding
to the text that also mention that imported package items can be used in
parameter declarations as well as port declarations.

I have uploaded version 4 of the proposal that removes the footnote from
non-ANSI headers, updates the wording of the footnote, and adds the
mention of parameters to the text.  Also, I changed the example from
having two package import statements in the module header to a single
import statement that imports two packages.

I have also deleted old versions of the proposal.

Stu
~~~~~~~~~~~~~~~~~~~~~~~~~
Stuart Sutherland
Sutherland HDL, Inc.
stuart@sutherland-hdl.com
503-692-0898
 

> -----Original Message-----
> From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com]
> Sent: Thursday, November 29, 2007 12:20 AM
> To: stuart@sutherland-hdl.com; sv-bc@server.eda.org
> Subject: RE: [sv-bc] e-mail ballot: respond by Dec 3, 8am PST
> 
> I think the proposal for 329 still has the following problem:
> 
> The BNF footnote says,
> 
> "A package_import_declaration in a module, interface, program header 
> shall be followed by a parameter_port_list or 
> list_of_port_declarations, or both."
> 
> That footnote appears in both the ansi and nonansi_headers.
> 
> But in nonansi_headers, a list_of_ports is used, not 
> list_of_port_declarations. Furthermore, list_of_ports has a 
> non-optional set of parentheses.
> 
> So the footnote is both wrong and unnecessary for nonansi_headers. 
> 
> 
> Less important is that the proposal says,
> 
> "Declarations such as typedefs and constants declared in packages can 
> be referenced in module, interface or program port declarations"
> 
> I think that should be "parameter or port declarations".
> 
> 
> Thanks,
> Shalom
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
> 
> This e-mail and any attachments may contain confidential material for 
> the sole use of the intended recipient(s). Any review or distribution 
> by others is strictly prohibited. If you are not the intended 
> recipient, please contact the sender and delete all copies.
> 


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


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