"corresponding format specification" means any format specification that would be applied to that expression. Currently, that correspondence is defined elsewhere to be by position in a format string. The rules for each format specification define which expression types are legal. So "corresponding" is a necessary but not sufficient condition. A new proposal has been uploaded to take care of the 'literal' ordering, and to address issues from the last sv-bc meeting. Dave -----Original Message----- From: Bresticker, Shalom [mailto:shalom.bresticker@intel.com] Sent: Monday, August 06, 2007 7:48 AM To: Rich, Dave; sv-bc@server.eda-stds.org Subject: RE: [sv-bc] Mantis 331 updated for Draft 3 Dave, Thanks for the work you have invested in this. Question: You add in 20.2.1 the following text: "Any argument expression of either a string data type or an unpacked array of byte data type that has no corresponding format specification shall be formatted as a character string. Any expression argument of any other unpacked data type that has no corresponding format specification shall be illegal." What do you mean here by "corresponding format specification"? Does "corresponding" mean only corresponding by position, or does it mean also corresponding in type? For example, if I write $display ("%d", string_variable);, is "%d" a corresponding (but not appropriate) format specification or not? Also, in the following sentence from Draft 3a: "The contents of literal string arguments are output literally except when certain escape sequences are inserted to display special characters or to specify the display format for a subsequent expression." Stu added the word 'literal'. (To be consistent with the rest of the LRM, it should be "string literal" instead of "literal string".) By doing so, the sentence excludes string data types. That should be fixed. Thanks, Shalom > -----Original Message----- > From: owner-sv-bc@server.eda.org > [mailto:owner-sv-bc@server.eda.org] On Behalf Of Rich, Dave > Sent: Saturday, July 14, 2007 9:34 AM > To: sv-bc@server.eda-stds.org > Subject: [sv-bc] Mantis 331 updated for Draft 3 > > Mantis 331 - Update $display and other file I/O system tasks > for aggregate data type > > has been updated for draft 3. That section when through > substantial changes, so please review carefully. > > http://www.eda-stds.org/svdb/view.php?id=331 > > Dave -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Mon Aug 6 08:35:00 2007
This archive was generated by hypermail 2.1.8 : Mon Aug 06 2007 - 08:35:08 PDT