view release on metacpan or  search on metacpan

share/PerlCritic/Critic/Policy/Variables/ProhibitPunctuationVars.pm  view on Meta::CPAN

  $| = undef;                      #not ok

  use English qw(-no_match_vars);
  local $OUTPUT_AUTOFLUSH = undef; #ok

=head1 CONFIGURATION

The scratch variables C<$_> and C<@_> are very common and are pretty
well understood, so they are exempt from this policy.  The same goes
for the less-frequently-used default filehandle C<_> used by stat().
All the regexp capture variables (C<$1>, C<$2>, ...) are exempt too.
C<$]> is exempt because there is no L<English|English> equivalent and
L<Module::CoreList|Module::CoreList> is based upon it.

You can add more exceptions to your configuration.  In your
perlcriticrc file, add a block like this:

  [Variables::ProhibitPunctuationVars]
  allow = $@ $!

share/SpamAssassin/easy_ham_2/00245.1a6c31f4aa59dc224123471dd267a63f  view on Meta::CPAN

  | > quickie for shell scripters:
  | > How do I find out the time a file was created at?
  |  
  |  There is no canonical test, and the information is not necessarily
  |  available.  [ ... ]  This information is also shown by ls -lc, but
  |  parsing ls' output requires a bit of effort. I'd rather recommend
  |  [ writing ] a short C program to access the file status directly,
  |  and output the ctime directly (seconds since the epoch, i.e. perfect
  |  |  for numerical comparison).

 some systems have a stat(1) tool --- don't think it's GNU --
 which, when given the `-t' option, does exactly what Lars is
 suggesting:

   $ stat -t /etc/motd
   /etc/motd 21 8 81a4 0 0 303 79 1 0 0 1028070983 830730492 1013296719

 minor problem is the `-t' format is not actually explained in
 the man page, but its fairly easy to work out (or you can just
 look at the source).  also, since the filename is printed as
 the first "field", bizarre filenames (e.g., ones which contain