Report for Ingres-Utility-Netutil-0.03

Back
From: Slaven Rezić (SREZIC) 
Subject: FAIL Ingres-Utility-Netutil-0.03 5.24.4 RC1 GNU/Linux
Date: 2018-03-30T09:52:40Z

This distribution has been tested as part of the CPAN Testers
project, supporting the Perl programming language.  See
http://wiki.cpantesters.org/ for more information or email
questions to cpan-testers-discuss@perl.org


--
Dear Joner Cyrre Worm,

This is a computer-generated report for Ingres-Utility-Netutil-0.03
on perl 5.24.4, created by CPAN-Reporter-1.2018.

Thank you for uploading your work to CPAN.  However, there was a problem
testing your distribution.

If you think this report is invalid, please consult the CPAN Testers Wiki
for suggestions on how to avoid getting FAIL reports for missing library
or binary dependencies, unsupported operating systems, and so on:

http://wiki.cpantesters.org/wiki/CPANAuthorNotes

Sections of this report:

    * Tester comments
    * Program output
    * Prerequisites
    * Environment and other context

------------------------------
TESTER COMMENTS
------------------------------

Additional comments from tester:

none provided

------------------------------
PROGRAM OUTPUT
------------------------------

Output from './Build test':

# Testing Ingres::Utility::Netutil 0.03
t/00.load.t ....... ok

#   Failed test 'Test::Perl::Critic for "blib/lib/Ingres/Utility/Netutil.pm"'
#   at /opt/perl-5.24.4-RC1/lib/site_perl/5.24.4/Test/Perl/Critic.pm line 121.
# 
#   Subroutine prototypes used at line 115, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 116, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 117, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 118, column 2.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 118, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 118, column 26.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 119, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 119, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 120, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 122, column 10.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 124, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 125, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 125, column 23.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 125, column 41.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 126, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 126, column 23.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 126, column 41.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 126, column 59.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 127, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 128, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 128, column 23.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 128, column 42.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 129, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 129, column 23.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 129, column 42.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 129, column 61.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 132, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 134, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 135, column 11.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 137, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 139, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 140, column 6.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 141, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 143, column 6.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 144, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 147, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 147, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 147, column 17.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 149, column 5.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 149, column 5.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 150, column 5.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 150, column 5.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 150, column 46.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 150, column 46.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 153, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 153, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Subroutine "new" called using indirect syntax at line 153, column 18.  See page 349 of PBP.  (Severity: 5)
#   Use of low precedence operators is not allowed at line 154, column 21.  Replace low precedence operators with the high precedence substitutes.  (Severity: 5)
#   "return" statement with explicit "undef" at line 156, column 25.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 158, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 158, column 15.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 158, column 15.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 159, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 160, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 161, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 162, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 162, column 17.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 162, column 32.  (no explanation).  (Severity: 5)
#   Use of low precedence operators is not allowed at line 163, column 9.  Replace low precedence operators with the high precedence substitutes.  (Severity: 5)
#   "return" statement with explicit "undef" at line 165, column 13.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 167, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 168, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 170, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 171, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 172, column 5.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 172, column 5.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 172, column 26.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 173, column 5.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 173, column 5.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 173, column 26.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 174, column 5.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 174, column 5.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 174, column 27.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 175, column 5.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 175, column 5.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 176, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 186, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 186, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 187, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 188, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 188, column 13.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 188, column 13.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 189, column 9.  (no explanation).  (Severity: 5)
#   Use of low precedence operators is not allowed at line 189, column 14.  Replace low precedence operators with the high precedence substitutes.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 190, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 191, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 195, column 1.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 196, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 197, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 197, column 13.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 197, column 13.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 198, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 199, column 9.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 199, column 9.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 200, column 14.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 200, column 20.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 200, column 20.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 202, column 33.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 203, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 205, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 206, column 2.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 206, column 13.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 207, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 207, column 18.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 207, column 18.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 207, column 38.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 207, column 38.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Use of low precedence operators is not allowed at line 208, column 9.  Replace low precedence operators with the high precedence substitutes.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 209, column 48.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 210, column 13.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 216, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 216, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 217, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 218, column 5.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 219, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 219, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 219, column 27.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 220, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 221, column 3.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 223, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 223, column 28.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 224, column 17.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 225, column 13.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 225, column 26.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 226, column 19.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 228, column 21.  (no explanation).  (Severity: 5)
#   Use of low precedence operators is not allowed at line 228, column 31.  Replace low precedence operators with the high precedence substitutes.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 228, column 35.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 229, column 17.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 229, column 30.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 230, column 23.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 234, column 12.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 239, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 239, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 240, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 241, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 242, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 243, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 244, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 246, column 12.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 247, column 9.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 251, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 253, column 6.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 253, column 6.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 253, column 29.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 254, column 17.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 255, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 257, column 8.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 257, column 8.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 260, column 8.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 260, column 8.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 261, column 3.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 261, column 3.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 263, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 263, column 16.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 263, column 16.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 264, column 14.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 264, column 25.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 264, column 25.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 265, column 3.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 265, column 3.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 268, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 268, column 16.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 268, column 23.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 268, column 23.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 269, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 269, column 28.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 270, column 12.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 286, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 286, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 287, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 288, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 289, column 6.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 290, column 7.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 291, column 7.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 293, column 17.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 296, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 297, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 297, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 298, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 298, column 31.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 298, column 31.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 299, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 299, column 18.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 300, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 300, column 16.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 300, column 16.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 301, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 301, column 16.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 302, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 302, column 16.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 302, column 38.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 302, column 43.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 302, column 43.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 302, column 62.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 304, column 5.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 304, column 5.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 304, column 28.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 305, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 305, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 306, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 306, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 307, column 19.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 325, column 1.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 326, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 327, column 12.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 346, column 1.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 347, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 348, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 349, column 6.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 350, column 7.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 351, column 7.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 353, column 17.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 356, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 357, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 358, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 359, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 360, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 360, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 361, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 361, column 34.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 361, column 34.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 362, column 2.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 362, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 363, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 363, column 15.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 363, column 15.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 364, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 364, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 365, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 365, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 365, column 37.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 365, column 42.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 365, column 42.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 365, column 61.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 366, column 5.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 366, column 5.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 366, column 28.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 367, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 367, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 368, column 19.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 386, column 1.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 387, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 388, column 12.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 418, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 418, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 419, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 420, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 421, column 6.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 422, column 6.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 424, column 13.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 426, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 427, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 429, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 431, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 432, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 434, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 436, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 437, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 439, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 442, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 443, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 444, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 444, column 18.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 445, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 445, column 15.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 445, column 15.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 446, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 446, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 447, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 447, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 447, column 37.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 447, column 42.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 447, column 42.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 447, column 61.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 448, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 449, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 449, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 450, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 450, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 451, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 451, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 452, column 19.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 471, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 471, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 472, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 473, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 474, column 6.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 475, column 6.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 477, column 13.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 479, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 480, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 482, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 484, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 485, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 487, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 489, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 490, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 492, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 494, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 495, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 497, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 500, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 501, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 501, column 18.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 502, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 502, column 15.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 502, column 15.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 503, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 503, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 504, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 504, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 504, column 37.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 504, column 42.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 504, column 42.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 504, column 61.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 505, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 505, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 506, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 506, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 507, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 507, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 508, column 19.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 524, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 524, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 525, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 526, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 527, column 6.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 528, column 6.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 530, column 13.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 532, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 533, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 535, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 537, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 538, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 538, column 18.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 539, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 539, column 15.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 539, column 15.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 540, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 540, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 541, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 541, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 541, column 37.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 541, column 42.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 541, column 42.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 541, column 61.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 542, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 542, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 543, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 543, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 544, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 544, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 545, column 19.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 564, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 564, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 565, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 566, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 567, column 6.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 568, column 6.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 570, column 13.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 572, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 573, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 575, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 577, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 578, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 580, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 582, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 583, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 585, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 587, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 588, column 8.  (no explanation).  (Severity: 5)
#   "return" statement with explicit "undef" at line 590, column 9.  See page 199 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 592, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 593, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 593, column 18.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 594, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 594, column 15.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 594, column 15.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 595, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 595, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 596, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 596, column 15.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 596, column 37.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 596, column 42.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 596, column 42.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 596, column 61.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 597, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 597, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 598, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 598, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 599, column 2.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 599, column 2.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 600, column 19.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 604, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 604, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 605, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 606, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 607, column 8.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 608, column 2.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 609, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 609, column 18.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 610, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 610, column 17.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 610, column 17.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 611, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 611, column 17.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 612, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 612, column 17.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 612, column 39.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 612, column 44.  (no explanation).  (Severity: 5)
#   Private Member Data shouldn't be accessed directly at line 612, column 44.  Accessing an objects data directly breaks encapsulation and should be avoided.  Example: $object->{ some_key }.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 612, column 63.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 613, column 19.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 626, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 626, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 627, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 628, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 630, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 630, column 45.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 643, column 1.  (no explanation).  (Severity: 5)
#   Subroutine prototypes used at line 643, column 1.  See page 194 of PBP.  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 644, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 645, column 5.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 646, column 9.  (no explanation).  (Severity: 5)
#   Variable, subroutine, and package names have to be in CamelCase at line 646, column 42.  (no explanation).  (Severity: 5)
t/perlcritic.t .... 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/1 subtests 
t/pod-coverage.t .. ok
t/pod.t ........... ok

Test Summary Report
-------------------
t/perlcritic.t  (Wstat: 256 Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
Files=4, Tests=4,  1 wallclock secs ( 0.02 usr  0.03 sys +  1.14 cusr  0.27 csys =  1.46 CPU)
Result: FAIL
Failed 1/4 test programs. 1/4 subtests failed.

------------------------------
PREREQUISITES
------------------------------

Prerequisite modules loaded:

requires:

    Module         Need Have    
    -------------- ---- --------
    Carp           0    1.38    
    Expect::Simple 0    0.04    
    Test::More     0    1.302133


------------------------------
ENVIRONMENT AND OTHER CONTEXT
------------------------------

Environment variables:

    LANG = en_US.UTF-8
    LC_ALL = de_DE.UTF-8
    PATH = /usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/cpansand/bin/linux-gnu:/home/cpansand/bin/sh:/home/cpansand/bin:/usr/games:/home/cpansand/devel:/home/eserte/src/srezic-misc/scripts
    PERL5LIB = 
    PERL5OPT = 
    PERL5_CPANPLUS_IS_RUNNING = 12014
    PERL5_CPAN_IS_RUNNING = 12014
    PERL5_CPAN_IS_RUNNING_IN_RECURSION = 25821,12014
    PERLDOC = -MPod::Perldoc::ToTextOverstrike
    PERL_BATCH = yes
    PERL_CANARY_STABILITY_NOPROMPT = 1
    PERL_CPAN_REPORTER_CONFIG = /var/tmp/cpansmoker-1023/2018032909/cpanreporter_000_config.ini
    PERL_EXTUTILS_AUTOINSTALL = --defaultdeps
    PERL_PARALLEL_SMOKER = yes
    SHELL = /usr/bin/zsh
    TERM = screen
    TMPDIR = /var/tmp/cpansmoker-1023/2018032909

Perl special variables (and OS-specific diagnostics, for MSWin32):

    $^X = /opt/perl-5.24.4-RC1/bin/perl
    $UID/$EUID = 1023 / 1023
    $GID = 1023 1023
    $EGID = 1023 1023

Perl module toolchain versions installed:

    Module              Have    
    ------------------- --------
    CPAN                2.16    
    CPAN::Meta          2.150010
    Cwd                 3.74    
    ExtUtils::CBuilder  0.280230
    ExtUtils::Command   7.34    
    ExtUtils::Install   2.14    
    ExtUtils::MakeMaker 7.34    
    ExtUtils::Manifest  1.70    
    ExtUtils::ParseXS   3.35    
    File::Spec          3.74    
    JSON                2.97001 
    JSON::PP            2.97001 
    Module::Build       0.4224  
    Module::Signature   0.81    
    Parse::CPAN::Meta   2.150010
    Test::Harness       3.42    
    Test::More          1.302133
    YAML                1.24    
    YAML::Syck          1.30    
    version             0.9918  


--

Summary of my perl5 (revision 5 version 24 subversion 4) configuration:
   
  Platform:
    osname=linux, osvers=4.4.0-116-generic, archname=x86_64-linux
    uname='linux ubuntu16 4.4.0-116-generic #140-ubuntu smp mon feb 12 21:23:04 utc 2018 x86_64 x86_64 x86_64 gnulinux '
    config_args='-ds -e -Dprefix=/opt/perl-5.24.4-RC1 -Dcf_email=srezic@cpan.org'
    hint=recommended, useposix=true, d_sigaction=define
    useithreads=undef, usemultiplicity=undef
    use64bitint=define, use64bitall=define, uselongdouble=undef
    usemymalloc=n, bincompat5005=undef
  Compiler:
    cc='cc', ccflags ='-fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
    optimize='-O2',
    cppflags='-fwrapv -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include'
    ccversion='', gccversion='5.4.0 20160609', gccosandvers=''
    intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678, doublekind=3
    d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16, longdblkind=3
    ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
    alignbytes=8, prototype=define
  Linker and Libraries:
    ld='cc', ldflags =' -fstack-protector-strong -L/usr/local/lib'
    libpth=/usr/local/lib /usr/lib/gcc/x86_64-linux-gnu/5/include-fixed /usr/include/x86_64-linux-gnu /usr/lib /lib/x86_64-linux-gnu /lib/../lib /usr/lib/x86_64-linux-gnu /usr/lib/../lib /lib
    libs=-lpthread -lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lc -lgdbm_compat
    perllibs=-lpthread -lnsl -ldl -lm -lcrypt -lutil -lc
    libc=libc-2.23.so, so=so, useshrplib=false, libperl=libperl.a
    gnulibc_version='2.23'
  Dynamic Linking:
    dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E'
    cccdlflags='-fPIC', lddlflags='-shared -O2 -L/usr/local/lib -fstack-protector-strong'


Characteristics of this binary (from libperl): 
  Compile-time options: HAS_TIMES PERLIO_LAYERS PERL_COPY_ON_WRITE
                        PERL_DONT_CREATE_GVSV
                        PERL_HASH_FUNC_ONE_AT_A_TIME_HARD PERL_MALLOC_WRAP
                        PERL_PRESERVE_IVUV USE_64_BIT_ALL USE_64_BIT_INT
                        USE_LARGE_FILES USE_LOCALE USE_LOCALE_COLLATE
                        USE_LOCALE_CTYPE USE_LOCALE_NUMERIC USE_LOCALE_TIME
                        USE_PERLIO USE_PERL_ATOF
  Locally applied patches:
	RC1
  Built under linux
  Compiled at Mar 24 2018 19:56:23
  %ENV:
    PERL5LIB=""
    PERL5OPT=""
    PERL5_CPANPLUS_IS_RUNNING="12014"
    PERL5_CPAN_IS_RUNNING="12014"
    PERL5_CPAN_IS_RUNNING_IN_RECURSION="25821,12014"
    PERLDOC="-MPod::Perldoc::ToTextOverstrike"
    PERL_BATCH="yes"
    PERL_CANARY_STABILITY_NOPROMPT="1"
    PERL_CPAN_REPORTER_CONFIG="/var/tmp/cpansmoker-1023/2018032909/cpanreporter_000_config.ini"
    PERL_EXTUTILS_AUTOINSTALL="--defaultdeps"
    PERL_PARALLEL_SMOKER="yes"
  @INC:
    /opt/perl-5.24.4-RC1/lib/site_perl/5.24.4/x86_64-linux
    /opt/perl-5.24.4-RC1/lib/site_perl/5.24.4
    /opt/perl-5.24.4-RC1/lib/5.24.4/x86_64-linux
    /opt/perl-5.24.4-RC1/lib/5.24.4
    .