Alvaro Herrera <alvhe...@2ndquadrant.com> writes:
> One slight problem with this is the common port/*.c idiom would require
> an extra include:
> #ifndef FRONTEND
> #include "postgres.h"
> #else
> #include "postgres_fe.h"
> #include "pgassert.h" /* <--- new line required here */
> #endif /* FRONTEND */
> If this is seen as a serious issue (I don't think so) then we would have
> to include pgassert.h into postgres_fe.h which would make the whole
> thing pointless (i.e. the same as just having the definitions in c.h).
We'd only need to add that when/if the file started to use asserts,
so I don't think it's a problem. But still not sure it's better than
just putting the stuff in c.h.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
