Re: cleaning perl code
Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: "Hamlin, Garick L" <ghamlin@isc.upenn.edu>
Cc: Noah Misch <noah@leadboat.com>, Alvaro Herrera
<alvherre@2ndquadrant.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-04-16T14:34:39Z
Lists: pgsql-hackers
On 4/16/20 10:20 AM, Hamlin, Garick L wrote: > On Thu, Apr 16, 2020 at 08:50:35AM -0400, Andrew Dunstan wrote: >> It would also be more robust using non-greedy matching: > This seems more important. > I don't know how/where this is being used, but if it has input like: > > /* one */ > something; > /* two */ > > With the old expression 'something;' would be stripped away. > Is that an issue where this this is used? Why are we parsing > these headers? > It's not quite as bad as that, because we're doing it line by line rather than on a whole file that's been slurped in. Multiline comments are handled using some redo logic. But /* one */ something(); /* two */ would all be removed. Of course, we hope we don't have anything so horrible, but still ... cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Stop requiring an explicit return from perl subroutines
- 0516f94d18c5 13.0 landed
-
Use perl's $/ more idiomatically
- 8f00d84afc0d 13.0 landed
-
Use perl warnings pragma consistently
- 7be5d8df1f74 13.0 landed