$ wc -l *.p* | tail -n 1
  6949 total
$ grep "no warnings" *.pl | wc -l
8
[download]

Here's a one-liner where Perl emits two warnings - both wrong.

 
$ perl -le 'use warnings; print ("$_") for qw /foo, #bar/'
print (...) interpreted as function at -e line 1.
Possible attempt to separate words with commas at -e line 1.
[download]

And yes, I know what the warnings are for. And I know how to code around them. The warnings are still wrong though.
Perl --((8:>*

That still seems like bad form to me. Imagine someone comes along and tries to extend it...

use warnings; print ("$_")."blah" for qw /foo, #bar, BAZ/
[download]

Just because you can do something doesn't mean you should. (Not that I'm implying that you should never turn off warnings. The OP's code isn't one of those times though).