On Thu, Aug 16, 2012 at 04:48:34PM +0100, Peter Geoghegan wrote:
> I found a tool that Google authored that attempts to solve the same
> problems as pgrminclude does in our codebase. It's called "include
> what you use", and is based on Clang. The project is hosted here:
>
> http://code.google.com/p/include-what-you-use/
>
> I'm not suggesting that we should start using this tool instead of
> pgrminclude, because it has enough caveats of its own, and is mostly
> written with Google's C++ codebase in mind. However, it's worth being
> aware of. There is a useful analysis of the general problem in the
> README - "Why IWYU is Difficult" (you can probably just skip the
> extensive analysis of C++ templates as they relate to the problem
> there).
>
> The tool is authored by Craig Silverstein, Google's director of
> technology. If he believes that IWYU is a difficult problem, well, it
> probably is.
Good to know. We only use pgrminclude very five years or so, and Tom
isn't even keen on that.
I added the URL to our src/tools/pginclude/README.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ It's impossible for everything to be true. +
