OK, except that in "Any white-space characters preceding or following the macro replacement text are not considered part of the replacement," "replacement" does not appear in the current LRM text. If you use it here, then consistency demands using it elsewhere as well. How about "Any white space characters preceding or following the macro text are not considered part of the macro text"? Regards, Shalom ________________________________ From: Alsop, Thomas R Sent: Monday, November 26, 2007 11:54 AM To: Bresticker, Shalom; 'sv-bc@server.eda.org' Subject: RE: [sv-bc] 1339: (RESEND)`define behavior on trimming leading and trailing spaces in macros Okay I get it now. I thought part of the mantis was attempting to deal with multi-line macros and spaces accrued internally. You are right, this is considered "inside" the macro. So, that being the case, I think simple removing that last sentence should do the trick. We can talk about it briefly during the conference call. I have updated the Mantis item with a revised proposal. -Tom ________________________________ From: Bresticker, Shalom Sent: Thursday, November 22, 2007 5:10 PM To: Alsop, Thomas R; sv-bc@server.eda.org Subject: RE: [sv-bc] 1339: (RESEND)`define behavior on trimming leading and trailing spaces in macros Tom, Additionally, for multi-line macros any trailing white-space between the last token on a line and the newline before a backslash is not considered part of the replacement. [SB] I disagree with this. This is not trimming white space preceding or following the macro text, but rather in the middle of the macro text. I also tested three different implementations, and none of them did this. 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 Mon Nov 26 13:41:47 2007
This archive was generated by hypermail 2.1.8 : Mon Nov 26 2007 - 13:42:05 PST