I second this. We show warning counts on an internal tinderbox and it
just makes them artificially high. More "harmless" warnings means it's
easier to miss the harmful ones.
email@hidden wrote on 5/16/05, 1:20 PM:
> We're going to have to stay on GCC 3.3 for a while. Would it be
> possible for you to give us a way to selectively silence that
> warning? In a project with 100 targets this warning generates up to
> 300 extra lines in the parsed build output pane... We would have to
> patch nightly build scripts to ignore the warning, et.c., et.c...
--
Mike Pinkerton
Mac Weenie
email@hidden http://people.netscape.com/pinkerton/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
