<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Jun 5, 2013, at 10:04 AM, Frank Rehwinkel <<a href="mailto:frankrehwinkel@gmail.com">frankrehwinkel@gmail.com</a>> wrote:</div><blockquote type="cite"><div dir="ltr">Thanks for asking. I just want to make sure I understand your statement and question. On Darwin, you've always had __weak defined as <span style="font-family:arial,sans-serif;font-size:12.800000190734863px">__attribute__((objc_gc(weak))), even when __strong is defined as <empty>?</span><div>
<span style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br></span></div><div style=""><span style="font-family:arial,sans-serif;font-size:12.800000190734863px">If it is intentional, then I would say there is no specific problem. We can put a comment into the header file for GNUstep to explain why __weak is being undef'ed before it is defined as <empty>. (Without the undef, the build generates seemingly hundreds of warnings, obscuring other warnings that might be more meaningful.)</span></div>
<div style=""><span style="font-family:arial,sans-serif;font-size:12.800000190734863px"><br></span></div><div style=""><span style="font-family:arial,sans-serif;font-size:12.800000190734863px">If it is unintentional, then a change to clang would obviate the additional code in the GNUstep header and save a few seconds every time someone went to read through the logic of those __strong and __weak macro definitions.</span></div>
</div></blockquote><br></div><div>Why don't you just not #define __weak and __strong on Darwin?</div><div><br></div><div>John.</div><br></body></html>