Re: C++ compiler

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Claudio Freire <klaussfreire(at)gmail(dot)com>, Gaetano Mendola <mendola(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: C++ compiler
Date: 2013-06-25 03:03:42
Message-ID: 20130625030342.GF14698@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 25, 2013 at 10:32:42AM +0800, Craig Ringer wrote:
> > Anything supported by C99 and not other versions I would say. However,
> > my point is if done correctly we would state which features ahead of
> > time we are willing to use and make them part of the developer faq?
>
> If C++ is seriously being considered, I'd take a look at:
>
> http://gcc.gnu.org/codingconventions.html
>
> http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml
>
> and look into a stylechecker that warns when it finds usage of
> inappropriate features. Possibly combined with a useful static checker.
>
> A useful starting point might be https://en.wikipedia.org/wiki/Cpplint.
>
> http://clang-analyzer.llvm.org/ may also be interesting, though it's
> more of a static analysis tool and less of a source code lint.

Yes, we would need something like that.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Steve Singer 2013-06-25 03:16:14 Re: [PATCH] Fix conversion for Decimal arguments in plpython functions
Previous Message Bruce Momjian 2013-06-25 02:44:42 Re: C++ compiler