On Tue, Jan 30, 2007 at 12:11:22PM -0600, Jonathan Rockway wrote:
To be read from the unparsable/invalild config file? ;-)
If the config file was parsed OK there's no need to report errors.
Because there weren't any.
/me heads off to drop a cat with a buttered slice of toast tied to its
Le 30 janv. 07 à 19:11, Jonathan Rockway a écrit :
Chisel Wright wrote:
On Tue, Jan 30, 2007 at 09:58:00AM -, Carl Vincent wrote:
That's exactly what we need - outputting warnings at on of the
ConfigLoader levels loses the content of the error message. Could
always add a Keep Quiet
On Wednesday 01/31/2007 04:42 AM, Chisel Wright wrote:
/me heads off to drop a cat with a buttered slice of toast tied to its
back ...
Feet. Buttered toast tied to its feet.
l.
--
Leonard A. Jaffe
-
This transmission may contain information that is
On 31 Jan 2007, at 14:49, [EMAIL PROTECTED] wrote:
On Wednesday 01/31/2007 04:42 AM, Chisel Wright wrote:
/me heads off to drop a cat with a buttered slice of toast tied
to its back ...
Feet. Buttered toast tied to its feet.
Depends which way up the toast is.
--
Matt S Trout,
Chisel Wright wrote:
/me heads off to drop a cat with a buttered slice of toast tied to its
back ...
I tried this this morning. The cat won.
--
package JAPH;use Catalyst qw/-Debug/;($;=JAPH)-config(name = do {
$,.=reverse qw[Jonathan tsu rehton lre rekca Rockway][$_].[split //,
;$;]-[$_].q;
Chisel Wright wrote:
On Tue, Jan 30, 2007 at 09:58:00AM -, Carl Vincent wrote:
That's exactly what we need - outputting warnings at on of the
ConfigLoader levels loses the content of the error message. Could
always add a Keep Quiet option...
To be read from the unparsable/invalild
Hi everyone,
I've just spent an inordinate amount of time debugging a problem which
was actually caused by my Yaml config file not parsing properly.
Catalyst isn't helping much - all it does is skip out the line of debug
that says [debug] Loaded Config ... and that's easy to overlook.
I
On 29/01/07, Carl Vincent [EMAIL PROTECTED] wrote:
Hi everyone,
I've just spent an inordinate amount of time debugging a problem which
was actually caused by my Yaml config file not parsing properly.
Catalyst isn't helping much - all it does is skip out the line of debug
that says [debug]
Carl Vincent wrote:
I've patched my Config::Any (attached below) so it throws a warning. Not
sure if this would cause problems if it was included in the distributed
module...
This is something I've been worried about for a while. Config::Any
tries to load every config file with every backend,
On 29 Jan 2007, at 16:19, Carl Vincent wrote:
Hi everyone,
I've just spent an inordinate amount of time debugging a problem which
was actually caused by my Yaml config file not parsing properly.
Which is why I don't use YAML. Try JSON or COnfig::General for sanity.
I discovered that when
Jonathan Rockway a écrit :
Perhaps making ConfigLoader louder would help? If no config is loaded
(but ConfigLoader is loaded), then perhaps we need to
[warn] Config file found but failed to load. Errors
[warn] YAML_OMG_YOU_FORGOT_SOMETHING (Line 42, Column 32)
etc.
Carl Franks wrote:
How about a Test::YAML, in the same vein as Test::Pod, providing a
all_yaml_files_ok() rountine which accepts a list of files or
directories to check?
How's Test::YAML::Valid?
The uploaded file
Test-YAML-Valid-0.01.tar.gz
has entered CPAN as
file:
12 matches
Mail list logo
