Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.2/8.9.1) with ESMTP id KAA36727
	for <pgsql-interfaces@postgreSQL.org>;
	Thu, 4 Mar 1999 10:00:42 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id JAA28096;
	Thu, 4 Mar 1999 09:59:41 -0500 (EST)
To: "Christopher R. Jones" <cj@interlog.com>
cc: PostgreSQL Interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Postgre Perl on WIN NT 
In-reply-to: Your message of Thu, 04 Mar 1999 08:50:04 -0500
	<3.0.5.32.19990304085004.00961440@mail.interlog.com>
Date: Thu, 04 Mar 1999 09:59:40 -0500
Message-ID: <28094.920559580@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Christopher R. Jones" <cj@interlog.com> writes:
> I am trying to build the Perl module in WINNT with VC++ 6.0.
> Unfortunately, VC++ has reserved the work "keyword" which is defined in
> libgg-fe.h:

(rolls eyes...)  Microsoft have never been too concerned about adherence
to standards, have they?

> typedef struct _PQconninfoOption
> {
> char   *keyword;

Unfortunately PQconninfoOption is part of the exported API of libpq,
so if I rename that field I can expect to break existing application
code :-(.  I'm not eager to do that.  If it were a strictly internal
change then renaming the field would be OK.

You might look at VC's compiler switches to see if it has a mode
where it actually compiles ANSI C++, and not some other language.

			regards, tom lane