From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alex Pilosov <alex@acecape.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Plan for straightening out the include-file mess
Date: Thu, 08 Feb 2001 18:29:02 -0500
Message-ID: <13522.981674942@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.BSO.4.10.10102081746270.10185-100000@spider.pilosoft.com>
References: <Pine.BSO.4.10.10102081746270.10185-100000@spider.pilosoft.com>
Alex Pilosov <alex@acecape.com> writes:
> when I include files needed for SPI, it drags also a lot of other
> garbage in, which conflicts with other things (namely, trying to get a
> file to simultaneously include SPI and perl headers is impossible).
> I realise it might be a lot of pain to clean up, but, you may consider
> having a separate top-level include for SPI, which would not define (by
> default) things like DEBUG, USE_LOCALE, union semun, etc.
Unless you want to write SPI code that never calls elog(), it's gonna be
tough to avoid the conflict on DEBUG. I suppose sooner or later we'll
have to rename the elog severity symbols ... but it's not a change that
I'm looking forward to making.
In any case there's too much time pressure to consider wide-ranging code
changes for 7.1. Right now I don't want to do more than rearrange the
contents of a small number of include files.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, alex@acecape.com, pgsql-hackers@postgresql.org
Subject: Re: Plan for straightening out the include-file mess
In-Reply-To: <13522.981674942@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox