This module provides a simple means for generating an RFC 2822 compliant datetime string. (In case you care, they're not RFC 822 dates, because they use a four digit year, which is not allowed in RFC 822.)

This package two interfaces. Firstly Error provides a procedural
interface to exception handling. Secondly Error is a base class for
errors/exceptions that can either be thrown (for subsequent catch) or
simply be recorded.

This class implements a fully OO exception mechanism similar to Exception::Class or Class::Throwable. It provides a simple interface allowing programmers to declare exception classes. These classes can be thrown and caught. Each uncaught exception prints full stack trace if the default verbosity is increased for debugging purposes.

The features of 'Exception::Base':
* fast implementation of the exception class
* fully OO without closures and source code filtering
* does not mess with '$SIG{__DIE__}' and '$SIG{__WARN__}'
* no external run-time modules dependencies, requires core Perl modules only
* the default behavior of exception class can be changed globally or just for the thrown exception
* matching the exception by class, message or other attributes
* matching with string, regex or closure function
* creating automatically the derived exception classes (perlfunc/use interface)
* easily expendable, see Exception::System class for example
* prints just an error message or dumps full stack trace
* can propagate (rethrow) an exception
* can ignore some packages for stack trace output
* some defaults (i.e. verbosity) can be different for different exceptions

This module provides an API for creating a the File::ChangeNotify::Watcher
manpage subclass that will work on your platform.

Most of the documentation for this distro is in the
File::ChangeNotify::Watcher manpage.

File::Comments guesses the type of a given file, determines the format used for comments, extracts all comments, and returns them as a reference to an array of chunks. Alternatively, it strips all comments from a file.

Currently supported are Perl scripts, C/C++ programs, Java, makefiles, JavaScript, Python and PHP.

The plugin architecture used by File::Comments makes it easy to add new formats. To support a new format, a new plugin module has to be installed. No modifications to the File::Comments codebase are necessary, new plugins will be picked up automatically.

File::Comments can also be used to simply guess a file's type. It it
somewhat more flexible than File::MMagic and File::Type. File types in File::Comments are typically based on file name suffixes (*.c, *.pl, etc.). If no suffix is available, or a given suffix is ambiguous (e.g. if several plugins have registered a handler for the same suffix), then the file's content is used to narrow down the possibilities and arrive at a decision.