Hi Lisa: You will have seen the mail that I sent to Gord about the paragraph that you cited from 22.8. For the purposes of disable iff resolution, it is not necessary that the rule be aligned with that for name resolution of variables (which according to Draft4 22.8 stops at module boundaries). Searches for non-variable items can continue upward from module boundary. SV-BC may be working on changing this rule, and resolution of the disable iff does not have to align to the rule about variables that says that the upward search stops at module boundaries. I think we should add back into the 1648 proposal some language that says clearly that a default disable iff from an enclosing scope applies in a nested scope if the nested scope does not declare its own default disable iff. J.H. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Tue Nov 20 10:43:52 2007
This archive was generated by hypermail 2.1.8 : Tue Nov 20 2007 - 10:44:05 PST