[Padre-dev] Do we have to use Log::Log4perl?

[breno]

That's why I made Padre::Log. It is small and fast (or so I hope) and
it's already documented (including the proposed integration with
Padre, which is the only thing not implemented as it would fiddle with
Main.pm and Padre::Plugin::Devel.pm). It doesn't fill all of Gabor's
requirements (such as module-specific logging), but this can also be
arranged, if it is of interest.

But I won't touch it again unless you guys actually decide to give it
a shot, otherwise it's just wasted time.

Cheers,

garu

On Mon, Apr 6, 2009 at 6:29 PM, Adam Kennedy
<adamkennedybackup at gmail.com> wrote:
> The mention of Log4perl was tickling my spidey senses for a while, and
> I just remembered why.
>
> The thing is enormous, it takes over 3 meg of RAM just to load it up.
>
> This adds something like 8% more startup memory to Padre, just to do
> (optional) logging.
>
> Would using something similar but smaller be possible?
>
> For example, Jordan Adler's Log::Tiny was created specifically to be a
> super-small alternative to Log4perl...
>
> http://search.cpan.org/~jmadler/Log-Tiny-0.01/lib/Log/Tiny.pm
>
> That's just one example, but others might be ok as well.
>
> Or perhaps we can set up the logging so it's a compile-time feature?
> Something we do a restart for if you want to turn it on?
>
> Adam K
> _______________________________________________
> Padre-dev mailing list
> Padre-dev at perlide.org
> http://mail.perlide.org/mailman/listinfo/padre-dev
>