Re: [HACKERS] scan.l: check_escape_warning()

2008-01-14 Thread Tom Lane
Michael Meskes [EMAIL PROTECTED] writes: On Fri, Jan 11, 2008 at 10:41:17AM -0500, Tom Lane wrote: Perhaps there's some discrepancy between the ecpg and backend lexers as to where these are called? You're right. There is no way to (un)select standard conforming strings which makes up for the

Re: [HACKERS] scan.l: check_escape_warning()

2008-01-13 Thread Michael Meskes
On Fri, Jan 11, 2008 at 10:41:17AM -0500, Tom Lane wrote: Perhaps there's some discrepancy between the ecpg and backend lexers as to where these are called? You're right. There is no way to (un)select standard conforming strings which makes up for the difference. Thanks for pointing me into the

[HACKERS] scan.l: check_escape_warning()

2008-01-11 Thread Michael Meskes
Hi, could anyone please enlighten me whether this function is still needed? AFAICT check_escape_warning() only has significant action if warn_on_first_escape is true. This variable is set to true only on label xqstart, but to false on xestart. However, check_escape_warning() and

Re: [HACKERS] scan.l: check_escape_warning()

2008-01-11 Thread Tom Lane
Michael Meskes [EMAIL PROTECTED] writes: could anyone please enlighten me whether this function is still needed? AFAICT check_escape_warning() only has significant action if warn_on_first_escape is true. This variable is set to true only on label xqstart, but to false on xestart. However,

Re: [HACKERS] scan.l: check_escape_warning()

2008-01-11 Thread Andrew Dunstan
Michael Meskes wrote: Hi, could anyone please enlighten me whether this function is still needed? AFAICT check_escape_warning() only has significant action if warn_on_first_escape is true. This variable is set to true only on label xqstart, but to false on xestart. However,