Re: WIP: Rework access method interface - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WIP: Rework access method interface
Date
Msg-id CA+TgmoasbYD-YLRoYhc1ucW-HFe=gGD3VTS=XpNR1RcmA8g4HA@mail.gmail.com
Whole thread Raw
In response to Re: WIP: Rework access method interface  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Jan 16, 2016 at 12:32 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Then we're going to end up with option A; and I suspect that we'll never
> bother with factoring out any common code, because it won't be worth the
> notational trouble if it involves common code that's in a different file
> in a different directory.

Since when is sharing code across files in different directories even
an iota more difficult than sharing code across files in the same
directory?

Sharing code across multiple files is only slightly more difficult
than sharing it within a file.  You just have to create a header file
in the appropriate place and stick the necessary declarations in
there.  I'll admit that's some work, but it's not usually very much.
After that, where the header gets included from really makes no
difference.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Compiler warning in pg_am changes
Next
From: Tom Lane
Date:
Subject: Re: Compiler warning in pg_am changes