On Sat, Nov 21, 2009 at 11:59 AM, Peter Kasting <pkast...@google.com> wrote:
> There is another fix, which is to disable to warning within the file or
> globally for GCC versions less than X. GCC exposes a number of different
> macros and switches that let you determine the version precisely either from
> script or in the preprocessor, and we already have a file that holds
> compiler-specific magic.
> The reason this would be nice compared to the whitelist proposal is that it
> wouldn't produce false negatives. The assumption is that there are only a
> small number of these kinds of cases, so enumerating them is not going to do
> awful things to our code.
This works for warnings we know about now, but not warnings that will
occur in the future, which is the larger problem.
I'd say we break the automated Ubuntu builds every couple of weeks
(and get an additional report from users at about that same rate).
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
