1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
Source: liblog-loglite-perl
Section: perl
Priority: optional
Maintainer: Bart Martens <bartm@knars.be>
Build-Depends-Indep: perl (>= 5.6.0-16)
Build-Depends: cdbs, debhelper (>= 5), libio-lockedfile-perl
Standards-Version: 3.7.2
Package: liblog-loglite-perl
Architecture: all
Depends: ${perl:Depends}, libio-lockedfile-perl
Description: Perl module that facilitates lightweight logging
In order to have a log we have first to create a Log::LogLite object. The
Log::LogLite object is created with a logging level. The default logging level
is 5. After the Log::LogLite object is created, each call to the write method
may write a new line in the log file. If the level of the message is lower or
equal to the logging level, the message will be written to the log file. The
format of the logging messages can be controled by changing the template, and
by defining a default message. The class uses the IO::LockedFile class.
.
The Log::NullLogLite class is derived from the Log::LogLite class and
implement the Null Object Pattern to let us to use the Log::LogLite class with
null Log::LogLite objects. We might want to do that if we use a Log::LogLite
object in our code, and we do not want always to actually define a
Log::LogLite object (i.e. not always we want to write to a log file). In such
a case we will create a Log::NullLogLite object instead of the Log::LogLite
object, and will use that object instead. The object has all the methods that
the Log::LogLite object has, but those methods do nothing. Thus our code will
continue to run without any change, yet we will not have to define a log file
path for the Log::LogLite object, and no log will be created.
.
Homepage: http://search.cpan.org/~rani/Log-LogLite/
|
