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 <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
