Re: #include oddity in v7.0b3

Didier Verna <didier@xemacs.org> writes:
>         The file `libpq-fe.h' #include's the file `postgres_ext.h' using <>
> instead of "" (line 27). As a consequence, applications that just do:
> | #include <full/path/to/libpq-fe.h>

> can't build anymore because the file `postgres_ext.h' is not in the path.

>         What do you think ? Was this change intentional ?

It was.  Someone else complained that the other way didn't work for them.
At least from the point of libpq, I think they were right.

Offhand, if you do not put -I into your compile switches, I'd be
somewhat surprised that either way would work for you.  Certainly
hardcoding a full path into application source code is a completely
unportable way to do things...

            regards, tom lane