On Wed, Aug 03, 2005 at 08:31:25AM -0600, Michael Fuhr wrote:
ECPG seems to be a little overzealous with the new escape string syntax:
This comes from starting the string constant with ESCAPE_STRING_SYNTAX
in case there is '\' inside the string. Actually I have no idea at the
moment how that
Michael Meskes wrote:
On Wed, Aug 03, 2005 at 08:31:25AM -0600, Michael Fuhr wrote:
ECPG seems to be a little overzealous with the new escape string syntax:
This comes from starting the string constant with ESCAPE_STRING_SYNTAX
in case there is '\' inside the string. Actually I have no idea
It turns out I made a mistake in trying to be too smart about adding E''
escapes for ecpg strings that have backslashes. I have reversed the
attached patch to fix the problem. Thanks for the report.
---
Michael Fuhr
ECPG seems to be a little overzealous with the new escape string syntax:
% cat foo.pgc
int
main(void)
{
putchar('\n');
return 0;
}
% ecpg foo.pgc
% gcc -I`pg_config --includedir` -c foo.c
foo.pgc: In function `main':
foo.pgc:4: `E' undeclared (first use in this function)
foo.pgc:4:
