Tom Lane írta:
> Boszormenyi Zoltan <zb(at)cybertec(dot)at> writes:
>> in a continued effort for better Informix ESQL/C compatibility,
>> we added the "string" pseudo-type handling to ECPG.
>> - "string" has become a type name, reserved word in ECPG.
> This seems like a sufficient reason to reject the patch. Who knows
> what that will break? (I observe that it already broke a few of the
> ecpg regression tests, suggesting that using "string" as a variable
> name is hardly uncommon.)
> regards, tom lane
OK, let me retry. This version treats "string" as a non-reserved word,
and also discovers whether the PGC contains this construct below,
as in ecpg/tests/preproc/type.pgc:
exec sql type string is char;
typedef char string;
Now all regression tests pass unchanged and ECPG also accepts
without typedef, replacing "string" with "char".
I think it's acceptable.
Thanks in advance,
Bible has answers for everything. Proof:
"But let your communication be, Yea, yea; Nay, nay: for whatsoever is more
than these cometh of evil." (Matthew 5:37) - basics of digital technology.
"May your kingdom come" - superficial description of plate tectonics
Cybertec Schönig & Schönig GmbH
In response to
pgsql-hackers by date
|Next:||From: Pavel Stehule||Date: 2009-07-04 19:58:46|
|Subject: problem with varlena and extended type|
|Previous:||From: Tom Lane||Date: 2009-07-04 13:51:57|
|Subject: Re: ECPG support for string pseudo-type |