NAME
App::Framework::Base::Object::Logged - Error handling object with logging capabilities
SYNOPSIS
use App::Framework::Base::Object::Logged ;
DESCRIPTION
DIAGNOSTICS
Setting the debug flag to level 1 prints out (to STDOUT) some debug messages, setting it to level 2 prints out more verbose messages.
AUTHOR
Steve Price <sdprice at cpan.org>
BUGS
None that I know of!
INTERFACE
App::Framework::Base::Object::Logged->new([%args])
-
Create a new App::Framework::Base::Object::Logged.
The %args are specified as they would be in the set method, for example:
'mmap_handler' => $mmap_handler
The full list of possible arguments are :
'fields' => Either ARRAY list of valid field names, or HASH of field names with default values
App::Framework::Base::Object::Logged->init_class([%args])
-
Initialises the App::Framework::Base::Object::Logged object class variables. Creates a class instance so that these methods can also be called via the class (don't need a specific instance)
App::Framework::Base::Object::Logged->log(@str)
-
Log the string. If field 'logfn' is defined, calls that instead. If field 'logfile' is defined, appends string to that. Otherwise does nothing.
App::Framework::Base::Object::Logged->clear_log([%args])
-
Restart the logfile.
App::Framework::Base::Object::Logged->_do_log($filename, $str)
-
PRIVATE
Log the string or array of strings.
1 POD Error
The following errors were encountered while parsing the POD:
- Around line 29:
=over without closing =back