What if you got the warning message but couldn't
tell what it meant? That's what the
perldiag manpage is for. Warning texts need to be
concise because they're compiled into the
perl binary (the program that runs your Perl
code). But perldiag should list all the messages
you should ever get from Perl, along with a longer explanation of
what each one means, why it's a problem, and how to
fix it.
If you want to be ultimately lazy, you can add use
diagnostics; at the beginning of your program, and any
error message will look itself up in the documentation and display
the entire detailed message. Don't leave this in
production code, however, unless you like burning a lot of CPU cycles
every time your program starts, whether or not an error occurs.