What it says is that a wildcard import is overridden by a declaration or an explicit import. That is fine if you have a single wildcard import. The minor problem is that the sentence I quoted could be interpreted as implying that if an identifier is multiply wildcard imported, then the identifier is undefined and an error occurs if the identifier is used EVEN IF the identifier is explicitly declared or explicitly imported, since no such qualification is found in the sentence. Shalom ________________________________ From: Rich, Dave [mailto:Dave_Rich@mentor.com] Sent: Wednesday, May 24, 2006 10:02 AM To: Bresticker, Shalom; sv-bc@server.eda.org Subject: RE: [sv-bc] import p::* It says that just a few sentences before this one. An identifier can't be wildcard imported in the case you mention. ________________________________ From: owner-sv-bc@server.eda.org [mailto:owner-sv-bc@server.eda.org] On Behalf Of Bresticker, Shalom Sent: Tuesday, May 23, 2006 10:59 PM To: sv-bc@server.eda.org Subject: RE: [sv-bc] import p::* Hmmm, 19.2 says, "If the same identifier is wildcard imported into a scope from two different packages, the identifier shall be undefined within that scope, and an error results if the identifier is used." Strictly speaking, that statement should be qualified by saying that the identifier is also neither declared nor explicitly imported within the scope. ShalomReceived on Wed May 24 00:42:52 2006
This archive was generated by hypermail 2.1.8 : Wed May 24 2006 - 00:43:09 PDT