[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] compiler warning policy
|
-1. The warning is very useful if it catch an error before runtime and
it does most of the time. And you can always write
a code that won't have this warning, even if cost some redundant
checks. How many actually warnings we are talking about here?
You can always set it to ignore on some specific projects (such as
edc), but I won't do it for cdt.core, etc.
On Wed, Sep 1, 2010 at 5:49 PM, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
> In http://wiki.eclipse.org/CDT/policy, it's recommended that Potential null
> pointer access be set to 'warning'. The default is 'ignore'. I think the
> usefulness of this warning is too debatable to make it a recommendation. The
> compiler's ability to detect a possible null pointer use is too weak and
> enabling the warning results in many false positives, requiring developers
> to either add needless checks to the code, live with the warnings, or
> disable them at too large a scope (method). If no one objects, I'll remove
> that recommendation from the WIKI page.
>
> John
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
