This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [C++] Coding rule enforcement
- From: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
- To: Daniel Gutson <daniel dot gutson at tallertechnologies dot com>
- Cc: Jason Merrill <jason at redhat dot com>, Richard Biener <richard dot guenther at gmail dot com>, Nathan Sidwell <nathan at acm dot org>, GCC Patches <gcc-patches at gcc dot gnu dot org>, David Malcolm <dmalcolm at redhat dot com>
- Date: Mon, 21 Sep 2015 16:01:39 +0200
- Subject: Re: [C++] Coding rule enforcement
- Authentication-results: sourceware.org; auth=none
- References: <55F816F2 dot 5010209 at acm dot org> <CAFiYyc1yZnWf35p+w_eKXnKZOaAj9pgXufk8Ba53wH8dttJSjg at mail dot gmail dot com> <55F85357 dot 5000101 at gmail dot com> <55F8640B dot 4060804 at redhat dot com> <CAF5HaEXHha-0LjKQwhKRUqhON8L2_2VVNPYBEQeZoW0vT2OEQw at mail dot gmail dot com>
On 21 September 2015 at 15:46, Daniel Gutson
<daniel.gutson@tallertechnologies.com> wrote:
>
> FWIW, we could make this plugin in 2 weeks (w already have static
> checkers as plugins for our customers). I understand Nathan that you
> may have some deadlines, but if we could have the opportunity to
> implement it, we could accomplish a clean isolation of a particular
> business needs (despite I acknowledge that a warning about virtual
> inheritance may be useful for a broader audience). OTOH, a plugin can
> receive arguments, such as a configuration file which could point to
> specific sources or hints about where to apply the warning, or a
> suppression file, both things useful for large legacy code. IMVHO I
> think this is a superior solution.
> Please let me know if we could collaborate to get both a better gcc
> and a better static checker.
My opinion is that if people want to "donate" their plugins to the
FSF, they are willing to maintain them, and they are not overtly
complex or require any third-party software, they should be added to
the GCC repository and build/tested. They could serve as examples and
extra testing for the plugin framework, with the expectation that they
may get removed if they become unmaintained.
Cheers,
Manuel.