| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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. |
| Date: | 2011-09-05 14:02:23 |
| Message-ID: | CABUevEwk_uV-Gtm9DhszJWVcsUzj+T2+nYkYGQ0RzQm+mWhVzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Sep 5, 2011 at 15:55, Greg Stark <stark(at)mit(dot)edu> wrote:
> On Mon, Sep 5, 2011 at 2:52 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> Well, I assume we are done for another five years. The includes removed
>> were minimal, especially considering five years of work.
>>
>
> What I wouldn't mind seeing is a graph of all includes and what they
> include. This might help figure out what layering violations there are
> like the one that caused this mess. I think I've seen tools to do this
> already somewhere.
http://doxygen.postgresql.org will do some of that, but I think not
globally - but if you click into one header, I think it shows you the
map from that perspective.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-09-05 15:07:12 | Re: [COMMITTERS] pgsql: Clean up the #include mess a little. |
| Previous Message | Greg Stark | 2011-09-05 13:55:58 | Re: [COMMITTERS] pgsql: Clean up the #include mess a little. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-09-05 14:27:34 | CF 2011-09-15 Call for Reviewers |
| Previous Message | Greg Stark | 2011-09-05 13:55:58 | Re: [COMMITTERS] pgsql: Clean up the #include mess a little. |