;) You are right. I changed C::P::Unicode to C::P::Unicode::Encoding, and it
works again. for more details, you may browse here:
http://www.perlmonks.org/?node_id=844392
On Tue, Jun 15, 2010 at 7:05 AM, Tomas Doran wrote:
>
> On 14 Jun 2010, at 02:05, Xiao Yafeng wrote:
>
> Thanks for your advic
On 13 Jun 2010, at 18:53, J. Shirley wrote:
On Jun 13, 2010, at 3:56 AM, Christiaan Kras wrote:
Thanks. He suggests Catalyst::Log::Log4perl.
I guess I'll try both Catalyst::Log::Log4perl and
Log::Log4perl::Catalyst then.
Christiaan Kras
The cspec issues can (in most cases) be safely ig
On 14 Jun 2010, at 02:05, Xiao Yafeng wrote:
Thanks for your advice. I've solved it.
Woo! \o/
Just for my information, what was the correct fix? Did
C::P::Unicode::Encoding work better for you?
Cheers
t0m
___
List: Catalyst@lists.scsys.co.uk
On Sat, 2010-06-12 at 18:05 -0500, w...@serensoft.com wrote:
> Catalyst (and Chaining in particular) is really, really sweet!
> Enjoying the exploration immensely. So here's our next puzzle:
> But that just gives
> Delta (inactive)
> Is there a way to include DISABLED options without s/// after
>
On Sun, Jun 13, 2010 at 11:14:44AM +0200, Christiaan Kras wrote:
[...]
> I've found and tried Catalyst::Plugin::Log4perl::Simple but when using the
> module Catalyst warns about it using NEXT. So I'm wondering if it's smart
> to use it in its current state.
That's one of my modules, a very crude h
