in reply to Re^2: Module Renaming Suggestions
in thread Module Renaming Suggestions

If that is the major feature of your module (and the main difference from other logging modules), how about a name like Log::Formatted?

In fact, I think your module is more complicated than it needs to be since you definitely want to control formatting, so *::Simple just isn't right. In the odd case that *::Simple would be appropriate, it wouldn't be for a module that requires extra work of setting up callbacks or denoting formats. A truly simple module would do that for you.

--
brian d foy <brian@stonehenge.com>

Replies are listed 'Best First'.
Re^4: Module Renaming Suggestions
by TGI (Parson) on Jul 02, 2005 at 16:30 UTC

    I am becoming convinced on the simple issue.

    Callbacks aren't required. The simplest usage would be: 

    my $log = Log::Simple->('path/to/file.log');
$log->open;

foreach my $stuff (@ARGV) {
    $log->entry("Stuff happened: $stuff");
}

$log->exit("Bad stuff happened", 999);

    [download]

    The standard formatter just sticks a timestamp on each line and prints it. If you don't define a default formatter with format, open, or new, the standard formatter will be used. If you do supply a default formatter, you can access the standard format for an entry by using 'standard' as the format argument.

    I have been thinking about some variant of 'Format' for the name. Because it gets at what this module does that is different from the many other logging modules. The other option I've been considering is something like WithCallbacks. But I haven't on anything that works well.


    TGI says moo

[reply]
[d/l]

In Section Meditations