Robert Haas wrote: > I personally think that's getting our priorities backwards, but > there's clearly a spectrum in terms of how much people care about the > cost of partial compiles, and I'm clearly all the way on one end of > it. I don't like having to think hard about where a function > prototype is or should be, and getting more consistency there would, > for me, outweigh all other considerations.
fmgr.h is a nasty header which would do well to avoid including in other headers as much as possible; it makes compilation in frontend environment impossible. For headers that don't otherwise need fmgr.h, my preference is to keep the SQL-callable declarations in builtins.h or some other dedicated header. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
