Re: [HACKERS] Note about include files]

2000-10-07 Thread Bruce Momjian
> The file "postgres.h" (or "c.h" or "config.h", whatever is used) needs to > be the very *first* file included by each source file. Next time you > touch a source file, please check that this is the case. > > The obvious failure mode is that if config.h redefines const, volatile, or > inline th

Re: [HACKERS] Note about include files

2000-10-02 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > On a related note, does anyone know why the on_proc_exit and on_shmem_exit > hooks use a second argument of type `caddr_t' rather than, say, void*, > char*, Datum, ...? This artifact is the cause of about two thirds of the > compile errors in the ped

Re: [HACKERS] Note about include files

2000-10-02 Thread Alfred Perlstein
* Peter Eisentraut <[EMAIL PROTECTED]> [001002 02:51] wrote: > The file "postgres.h" (or "c.h" or "config.h", whatever is used) needs to > be the very *first* file included by each source file. Next time you > touch a source file, please check that this is the case. > > The obvious failure mode

[HACKERS] Note about include files

2000-10-02 Thread Peter Eisentraut
The file "postgres.h" (or "c.h" or "config.h", whatever is used) needs to be the very *first* file included by each source file. Next time you touch a source file, please check that this is the case. The obvious failure mode is that if config.h redefines const, volatile, or inline then it will c