> The proposal says explicitly, "`__FILE__ expands to the name of the current input file, in the form of a string literal." Yes, right. >Maybe the import statement is (although calling it a declaration is a misnomer, I think) I disagree. It's not a statement, it's a declaration. -- Brad -----Original Message----- From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com] Sent: Thursday, October 04, 2007 2:49 PM To: Brad Pierce; sv-bc@eda.org Subject: RE: [sv-bc] E-mail Ballot: Respond by Oct 14, 2007 8am PDT Brad, > 1464: Why the changes from 'm' to 'mm' and 'a' to 'aa'? The instance name 'a' was changed to avoid conflict with the net/variable of the same name declared in the same scope. > > 1588: Not clear whether `__FILE__ expands to a string literal, that > is, is the path bracketed with " characters? Why is it not clear? The proposal says explicitly, "`__FILE__ expands to the name of the current input file, in the form of a string literal." > 2024: OK, but a package_import_declaration really *is* a > declaration. Maybe the import statement is (although calling it a declaration is a misnomer, I think), but that does not mean the imported identifiers are declared in the importing scope. Regards, 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.Received on Thu Oct 4 14:54:01 2007
This archive was generated by hypermail 2.1.8 : Thu Oct 04 2007 - 14:55:35 PDT