Stu, OK, I agree that 'space character' means 0x20, not just white space, so your language is specific enough on that. Regarding stripping off the escape, 5.6.1 says "Neither the leading backslash character nor the terminating white space is considered to be part of the identifier. Therefore, an escaped identifier \cpu3 is treated the same as a nonescaped identifier cpu3." For example, the following is a legal declaration typedef enum {\typedef , \enum , \uwire } T; but the following is not typedef enum {\typedef , \enum , \T } T; -- Brad -----Original Message----- From: owner-sv-bc@eda.org [mailto:owner-sv-bc@eda.org] On Behalf Of Stuart Sutherland Sent: Monday, May 04, 2009 6:04 PM To: sv-bc@eda.org Subject: RE: [sv-bc] RE: E-mail Vote: Respond by Monday, May 11, 2009 8am PDT Brad, You stated: > SVDB 2678 ___Yes _X__No > http://www.eda.org/svdb/view.php?id=2678 > > not clear which whitespace character is required, should be more > specific and require '\040' > not clear enough about cases like > > typedef enum {\bronze , \silver , \gold } T; > The proposal specifies the "backslash and space characters", which I felt was clear which type of whitespace is being used. I would be fine with amending the proposal to say "backslash ( \ ) and space (ASCII 0x40) characters". Personally, I feel that if the user specifies an escape where it is not needed, tools should still return the name with that escape. As far as I know, the standard is silent on whether tools are allowed to strip off the escape when it is not needed, which, IMHO, makes it illegal to do so. If stripping off the escape is specified somewhere, then I am OK with amending the proposal to refer to that text for when .name returns the escaped form of the label. Both points will need to be discussed at the May 11 conference call, since the e-mail vote already has a mix of yes and no responses. Stu ~~~~~~~~~~~~~~ Stuart Sutherland stuart@sutherland-hdl.com (503) 692-0898 -- 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.Received on Mon May 4 18:54:58 2009
This archive was generated by hypermail 2.1.8 : Mon May 04 2009 - 18:55:11 PDT