If you want notes from all the modules you are using, and you are not
worried about global subroutine definitions or subroutine redefined
warnings, you may wish to specify that you want to search for all notes.
Set how much debugging you want. The bigger the number, the more verbose
(except zero, which is unlimited).
A note can specify what level it is.
By setting the level you want, Devel::Messenger will know to ignore notes with a higher level than you specified.
Sometimes it is useful to know where a note came from. This setting will
prepend the linenumber to the messages Devel::Messenger finds for you.
See also pkgname.
If you do not tell Devel::Messenger what to do with your messages, it will
just ignore them. You can specify where to send them by setting this
There are several ways Devel::Messenger can try to send you messages. These are described below:
If you want to know from which package a note is coming, you can have
Devel::Messenger prepend the package name to each message. If the note is
coming from package main (the default package), the filename shall be
If this is not enough information, you may also want to ask for a linenumber to be provided.
When you instruct Devel::Messenger::note, it tries to send you a message
telling you which version of Devel::Messenger you are using. You may not
wish to fill up your error log, or other files, with this version information.
In this case, you should tell Devel::Messenger to keep quiet about what
version it is.
Devel::Messenger likes to give you messages how you like them. With this
option, you can specify markup you wish to have wrapped around each note.
Accepts an ARRAY reference or a string.
If the second part of the wrapping text ends in a newline (\n), the note is chomped before being wrapped.
As explained above, notes can specify what level they are. The level could theoretically be from one all the way up to your integer limit.
However, levels could become almost meaningless if we allowed so many different levels.
My standard levels are:
1. Minimal information about what the program is doing. 2. Database interaction: connections, queries, number of records returned, et cetera. 3. In depth information about what the program is doing. 4. In depth information about database interaction. 5. In depth information about formatting. 6. In depth information about conversions. 7. In depth information about everything else.
Nathan Gray - email@example.com
Devel::Messenger is Copyright (c) 2001 Nathan Gray. All rights reserved.
You may distribute under the terms of either the GNU General Public License, or the Perl Artistic License.
|perl v5.20.3||MESSENGER (3)||2008-05-02|