Re: Cleaning up perl code
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Alexander Lakhin <exclusion@gmail.com>
Cc: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-07-02T01:11:46Z
Lists: pgsql-hackers
On Fri, May 24, 2024 at 02:09:49PM +0900, Michael Paquier wrote: > For now, I have staged for commit the attached, that handles most of > the changes from Alexander (msvc could go for more cleanup?). This one has been applied as of 0c1aca461481 now that v18 is open. > I'll look at the changes from Dagfinn after that, including if perlcritic > could be changed. I'll handle the first part when v18 opens up, as > that's cosmetic. I'm still biased about the second set of changes proposed here, though. ProhibitUnusedVariables would have benefits when writing perl code in terms of clarity because we would avoid useless stuff, but it seems to me that we should put more efforts into the unification of the errcodes parsing paths first to have a cleaner long-term picture. That's not directly the fault of this proposal that we have the same parsing rules spread across three PL languages, so perhaps what's proposed is fine as-is, at the end. Any thoughts or comments from others more familiar with ProhibitUnusedVariables? -- Michael
Commits
-
Clean up more unused variables in perl code
- dd569214aa7d 18.0 landed
-
Cleanup perl code from unused variables and routines
- 0c1aca461481 18.0 landed
-
Fix comment in 024_add_drop_pub.pl
- 53785d2a2aaa 17.0 landed