RE: [sv-bc] Mantis 1338 - Clarificaion on String literal behavior in macros

Hi,


________________________________

	From: Alsop, Thomas R 
	Sent: Monday, November 26, 2007 3:11 PM
	To: Bresticker, Shalom
	Cc: 'sv-bc@server.eda.org'
	Subject: RE: [sv-bc] Mantis 1338 - Clarificaion on String
literal behavior in macros
	
	

	Shalom,

	 

	One issue I have with the mail link you forwarded deals with
Rule 3:

	 

	Rule 3. You can use \" instead of " to get a quotation mark in
the text
	macro definition, but then Rule 1 does not apply, and then macro
	expansion WILL occur if a macro call or a formal argument name
is
	encountered. (What happens if " is followed by \" or the
reverse?)
	 

	I think you mean `" not \".  
	[SB] Of course, this was corrected in the continuation of the
thread.

	 

	 Unless you are proposing now that this be part of the proposal.
You note that there are other open items dealing with the backslash
character.  If so, let's let the other mantis items resolve them.  If
the meaning changes what we are doing with this proposal, then we can
address it.  From what I understand it shouldn't impact what we have
already proposed.
	[SB] I think the proposal should say that not only are macro
arguments replaced, but also embedded macro usages, i.e., the difference
between  

	 

	`define A `" `cucu `" // expands `cucu, then encloses it in
quotes

	and

	`define A " `cucu " // expands literally with no changes to "
`cucu "

	 

	Also, the text says, 

	'An `"  ...  indicates that the expansion should include an
actual quotation mark.' 

	 Besides that "should" should be "shall", that statement is true
for " as well as for `", so it should say something to the effect that
`" is replaced by ".

	 

	And I think the proposal should say something about what happens
if you have mixed `" and " in the macro text.

	 

	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.