Re: [COMMITTERS] pgsql: Clean up the #include mess a
little.
From:
Bruce Momjian <bruce(at)momjian(dot)us>
To:
Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>
Cc:
Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Stark <stark(at)mit(dot)edu>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject:
Re: [COMMITTERS] pgsql: Clean up the #include mess a
little.
On Wed, Sep 7, 2011 at 01:20:17AM +0300, Ants Aasma wrote:
> On Tue, Sep 6, 2011 at 10:18 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
> > I wonder what happens if files in the same subdir are grouped in a
> > subgraph. Is that possible?
>
> Possible, and done. Also added possivility to add .c files to the graph,
> coloring by subdir and possibility exclude nodes from the graph. I didn't yet
> bother to clean up the code - to avoid eye damage, don't look at the source.
>
> Bad news is that it doesn't significantly help readability for the all nodes
> case. See all_with_subgraphs.svgz. It does help for other cases.
> For example parsenodes.h.svgz has the result for
> render_includes.py --select='nodes/parsenodes.h+*-*' --subgraphs
> and execnodes.h.svgz for
> --subgraphs --select='nodes/execnodes.h+*-*'
Should we add this script and instructions to src/tools/pginclude?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
