<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>Le 15 août 2012 à 21:10, jahanian <<a href="mailto:fjahanian@apple.com">fjahanian@apple.com</a>> a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 15, 2012, at 12:04 PM, Jordan Rose 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 15, 2012, at 11:58 , jahanian <<a href="mailto:fjahanian@apple.com">fjahanian@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 15, 2012, at 11:49 AM, Jordan Rose 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; "><div>What <i>is</i> the unexpected behavior? Or what will it <i>not</i> do that I would expect it to do? (I forget what __private_extern__ is actually for.)</div><br><div>On Aug 15, 2012, at 11:42 , Fariborz Jahanian <<a href="mailto:fjahanian@apple.com">fjahanian@apple.com</a>> wrote:</div></div></blockquote></div><br><div>Depending on __private_extern__ decl. being in header file or main file, visibility attribute may or may not show up in the</div><div>generated code (and it may not be a tentative definition). See the radar for why Nick thinks this warning is needed to</div><div>get us out of the jam for this gcc compatible behavior.</div></div></blockquote><br></div><div>I think what I was trying to say is that the warning should be a little more explanatory. I don't have an alternative wording myself, though.</div></div></blockquote><br></div><div>I tried to make the warning as long and explanatory as possible. But, user may have to read the radar's long description to see</div><div>the rational for the warning. But, feel free if you can improve on the message.</div></div></blockquote><div><br></div><div>Would be fine if radar where visible by the user. Unfortunately, this is not the case…</div></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div>-- Jean-Daniel</div><div><br></div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></body></html>