<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 7, 2012, at 1:27 PM, Douglas Gregor wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 7, 2012, at 1:01 PM, jahanian <<a href="mailto:fjahanian@apple.com">fjahanian@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><font class="Apple-style-span" color="#00721e"><br></font></div><div>ARC has an error for weak ivar access; it doesn't cover any of the (more common) cases of ivar access that we still want to warn about with this warning.</div><div><br></div><div>So, I still think that we should not turn on/off this warning depending on whether the code is MRR/GC/ARC, because it has nothing to do with the memory model. Of course, if the ARC error for weak ivar access fails, we should not emit the warning, because the error is more important.</div></div></blockquote><div><br></div>Ok then. In r161458.</div><div>- fariborz</div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><br></div></blockquote></div><br></body></html>