Agreed. But as the third team on the project and with a few hundred files we didn't write, it's beyond our control. We just live with the pain.
On Feb 17, 2015, at 7:08 PM, Jens Alfke wrote: > >> On Feb 17, 2015, at 1:48 PM, Alex Zavatone <[email protected]> wrote: >> >> FWIW, I've resorted to pressing command 4 for the Issue Navigator, then >> clicked the little circle with the ! mark in it on the lower left of the >> window to only show the critical error without all the other non critical >> gibberish. This highlights the severe errors only. > > Hm, I just tried that and it doesn’t suppress any errors (including the > redundant/garbage ones like linker and dsymutil errors after a compiler > error.) All it does is suppress warnings, and if you’ve got warnings you > really should be fixing them as they occur* instead of letting them pile up > to the point of annoyance. (Me, I’m pretty zealous about using -Werror.) > > —Jens > > * Or if you have no control over the source code or it’s legacy crap that you > can’t clean up, then at least turn off the warnings for those source files. > I’ve got that going on in a couple of 3rd party libraries I build into my > project.
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
