On Aug 6, 2012, at 5:09 PM, Jordan Rose wrote: > Why does this only warn under non-GC?
I don't know. This is an old GCC option and brought it over as-is to clang. I don't have the original gcc radar to look for the rational. Could be that under GC it is safe to do direct assignment while with the advent of properties, users warn to catch such accesses and use the property syntax which controls the ivar access with its own APIs (think atomic vs non-atomic). - Fariborz > > Jordan > _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
