On Wed, May 26, 2010 at 11:01 AM, alvherre <alvherre@commandprompt.com> wrote:
> Excerpts from Robert Haas's message of mié may 26 07:20:30 -0400 2010:
>
>> I still feel that we'd be better off putting all the functions that
>> use the same design pattern in a single file, rather than spreading
>> them out all over the backend. It's true that that one file will then
>> depend on all the catalog stuff, but it actually can limit
>> dependencies a little bit on the other end, because if someone wants
>> to call a bunch of these functions from the same file, they only need
>> to include the one header where they are all declared, rather than all
>> the individual files that contain the individual functions.
>
> This doesn't buy you anything, because that one header will likely have
> to #include all the other headers anyway. And if this is so, then all
> those headers will now be included in all files that require even a
> single one of these functions.
Well, at any rate, I'm giving up on the argument.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company