From: | "Luke Lonergan" <llonergan(at)greenplum(dot)com> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | "PostgreSQL-patches" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: backslashes in pgindent |
Date: | 2005-07-16 05:34:35 |
Message-ID: | BEFDEA7B.8C0E%llonergan@greenplum.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce,
On 7/15/05 9:59 PM, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> Actually, mine returns ')' too for the last command. I didn't copy
> that into the email. How about the top tests? Notice I get an error on
> the first one without the backslash. Are you OK escaping '(' but not
> ')'? That might be a solution.
You know, I'm not sure - I don't know the intended meaning of this line:
awk ' BEGIN {line1 = ""; line2 = ""}
{
line2 = $0;
if (NR >= 2)
print line1;
if (NR >= 2 &&
line2 ~ "^{[ ]*$" &&
line1 !~ "^struct" &&
line1 !~ "^enum" &&
line1 !~ "^typedef" &&
line1 !~ "^extern[ ][ ]*\"C\"" &&
line1 !~ "=" &&
=====> line1 ~ "\)")
print "int pgindent_func_no_var_fix;";
line1 = line2;
}
END
Is the escaped paren within "" meant to be a literal?
- Luke
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2005-07-16 10:07:41 | Re: [HACKERS] 4 pgcrypto regressions failures - 1 unsolved |
Previous Message | Bruce Momjian | 2005-07-16 04:59:16 | Re: backslashes in pgindent |