Re: building pg_dump doesn't work - Mailing list pgsql-hackers

From Tom Lane
Subject Re: building pg_dump doesn't work
Date
Msg-id 1335.1236179485@sss.pgh.pa.us
Whole thread Raw
In response to building pg_dump doesn't work  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: building pg_dump doesn't work  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Perhaps this could be made less ugly by only having the ScanKeywords 
> array in the .c file, and #including that into other .c files in 
> src/backend/parser, ecpg and pg_dump.

What I'd suggest is something similar to the design of the errcodes.h
header: create a header file containing just the list of PG_KEYWORD
macro calls, and have the different users #include it after defining
that macro appropriately.  Having .c files include other .c files is
usually best avoided on least-surprise grounds.

> Not sure what to do about ScanKeywordLookup function.

Yeah, duplicating that function is a bit annoying.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: building pg_dump doesn't work
Next
From: Heikki Linnakangas
Date:
Subject: Re: building pg_dump doesn't work