Re: cleaning perl code
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-04-11T15:14:52Z
Lists: pgsql-hackers
Noah Misch <noah@leadboat.com> writes: > In summary, among those warnings, I see non-negative value in "Code before > warnings are enabled" only. While we're changing this, I propose removing > Subroutines::RequireFinalReturn. If it's possible to turn off just that warning, then +several. It's routinely caused buildfarm failures, yet I can detect exactly no value in it. If there were sufficient cross-procedural analysis backing it to detect whether any caller examines the subroutine's result value, then it'd be worth having. But there isn't, so those extra returns are just pedantic verbosity. regards, tom lane
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