Re: Improving the notation for ecpg.addons rules
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-08-20T18:33:23Z
Lists: pgsql-hackers
Attachments
- check-usage-of-parse.pl-hash-tables.patch (text/x-diff) patch
I wrote: > Michael Paquier <michael@paquier.xyz> writes: >> It looks like %replace_line expects all its elements to have one space >> between each token, still this is not enforced with a check across its >> hardcoded elements? > Yeah, I was wondering about that. I wouldn't do it exactly like > that, but with a check that the entry gets matched somewhere. Here's a patch for that (again based on the other patch series). This did not turn up anything interesting, but it's probably worth keeping. regards, tom lane
Commits
-
ecpg: invent a saner syntax for ecpg.addons entries.
- dbedc461b4e7 18.0 landed
-
ecpg: add cross-checks to parse.pl for usage of internal tables.
- d2f41b4621de 18.0 landed