Re: [9.3 bug fix] ECPG does not escape backslashes - Mailing list pgsql-hackers

From MauMau
Subject Re: [9.3 bug fix] ECPG does not escape backslashes
Date
Msg-id 5F5F408615BF40AA924506241C5B569E@maumau
Whole thread Raw
In response to Re: [9.3 bug fix] ECPG does not escape backslashes  (Michael Meskes <meskes@postgresql.org>)
List pgsql-hackers
From: "Michael Meskes" <meskes@postgresql.org>
> So that means MauMau was right and backslashes have to be escaped in 
> filenames
> in #line directives, right? Apparently my examples were badly chosen as I
> didn't see an error no matter how many backslashes I had.

Yes, the below examples shows the case:

[maumau@myhost ~]$ touch ab\\c/a.pgc
[maumau@myhost ~]$ ecpg ab\\c/a.pgc
[maumau@myhost ~]$ gcc -c -I/tuna/pgsql/include ab\\c/a.c
ab\c/a.c:8:9: warning: unknown escape sequence '\c'
[maumau@myhost ~]$


> Committed to 8.4, 9.0, 9.1, 9.2 and HEAD.

Thank you very much for your quick support.

Regards
MauMau




pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: WITH CHECK OPTION for auto-updatable views
Next
From: Andres Freund
Date:
Subject: Re: changeset generation v5-01 - Patches & git tree