| From: | John Morris <john(dot)morris(at)crunchydata(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, Bohdan Mart <mart(dot)bogdan(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, "postgres(at)coyotebush(dot)net" <postgres(at)coyotebush(dot)net>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Subject: | Re: Where can I find the doxyfile? |
| Date: | 2024-02-07 17:26:39 |
| Message-ID: | CYXP222MB0947FE38949AF6E466ABBAA2A0452@CYXP222MB0947.NAMP222.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> Maybe this is something that can be tweaked on the doxygen side?
I’ll look into that idea. Doxygen is a separate project with its own developers to persuade. I could imagine a special “C” or “C++” mode. I wanted to keep things simple, and the filter mechanism is how they extend doxygen to support other languages.
One alternative is to add the filter to doxygen’s webpage. They currently list a number of filters, none of which address this particular issue. The filter would become a build dependency like doxygen itself.
In the meantime, I’d like to address Alvaro’s concern about generating artifacts. It’s a bit tedious, but a visual survey of the output may add confidence or show areas needing improvement.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-02-07 18:11:41 | Re: Testing autovacuum wraparound (including failsafe) |
| Previous Message | Nathan Bossart | 2024-02-07 17:15:54 | Re: common signal handler protection |