I don't encounter this warning often, but when I do it indicates a bug in my code.
I saw this at two my clients recently, one we turned use warinings on. Frankly I don't understand why even in 2018 some companies insist on not using warnings.
Perl Maven Pro - screencasts with articles
As a Perl Maven Pro subscriber you will enjoy a library of articles and screencasts.
Ad free browsing!
The articles contain topics such as Web Application Development, Object Oriented programming, testing, deployment, code walkthroughs, best practices, and many more subjects in Perl, and in related technologies.
The related technologies over HTML5, CSS3, JavaScript, Git, Subversion, vim, Unix/Linux shell, SQL and NoSQL just to name a few topic that I, as a Perl programmer find useful.
Subscriptions include all previous pro episodes.
In order to subscribe to the Perl Maven Pro, first register and login to the web site, and then pay via PayPal:
or
If you already have Perl Maven Pro subscription, you will need to login to access the articles.
Gabor who runs the Perl Maven site helps companies set up test automation, CI/CD
Continuous Integration and Continuous Deployment and other DevOps related
systems.