X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=p5sagit%2FConfig-Any.git;a=blobdiff_plain;f=lib%2FConfig%2FAny.pm;h=844af1b93a0476cc2a3746003b92ad8269701e16;hp=c7164cd0e97ce9141180547274771a60328db940;hb=fcfdc024cf1d514b70a03e954d553f6cef3983fb;hpb=ee6cd09bc61ac649cd49e630588815c232a9ea68 diff --git a/lib/Config/Any.pm b/lib/Config/Any.pm index c7164cd..844af1b 100644 --- a/lib/Config/Any.pm +++ b/lib/Config/Any.pm @@ -6,7 +6,7 @@ use warnings; use Carp; use Module::Pluggable::Object (); -our $VERSION = '0.20'; +our $VERSION = '0.31'; =head1 NAME @@ -33,16 +33,14 @@ to load configuration data from multiple different file formats. It supports XML JSON, Apache-style configuration, Windows INI files, and even Perl code. The rationale for this module is as follows: Perl programs are deployed on many different -platforms and integrated with many different systems. Systems administrators and end +platforms and integrated with many different systems. Systems administrators and end users may prefer different configuration formats than the developers. The flexibility -inherent in a multiple format configuration loader allows different users to make +inherent in a multiple format configuration loader allows different users to make different choices, without generating extra work for the developers. As a developer you only need to learn a single interface to be able to use the power of different configuration formats. -=head1 INTERFACE - -=cut +=head1 INTERFACE =head2 load_files( \%args ) @@ -54,15 +52,15 @@ configuration formats. C attempts to load configuration from the list of files passed in the C parameter, if the file exists. -If the C parameter is set, it is used as a callback to modify the configuration -data before it is returned. It will be passed a single hash-reference parameter which +If the C parameter is set, it is used as a callback to modify the configuration +data before it is returned. It will be passed a single hash-reference parameter which it should modify in-place. If the C parameter is defined, the loader will attempt to parse the file extension from each filename and will skip the file unless it matches a standard extension for the loading plugins. Only plugins whose standard extensions match the file extension will be used. For efficiency reasons, its use is encouraged, but -be aware that you will lose flexibility -- for example, a file called C +be aware that you will lose flexibility -- for example, a file called C containing YAML data will not be offered to the YAML plugin, whereas C or C would be. @@ -70,9 +68,9 @@ When the C parameter is defined, the loader will return a hash keyed on the file names, as opposed to the usual list of single-key hashes. C also supports a 'force_plugins' parameter, whose value should be an -arrayref of plugin names like C. Its intended use is to allow the use +arrayref of plugin names like C. Its intended use is to allow the use of a non-standard file extension while forcing it to be offered to a particular parser. -It is not compatible with 'use_ext'. +It is not compatible with 'use_ext'. You can supply a C hashref to pass special options to a particular parser object. Example: @@ -102,7 +100,7 @@ sub load_files { Config::Any->load_stems( { stems => \@stems, flatten_to_hash => 1 } ); C attempts to load configuration from a list of files which it generates -by combining the filename stems list passed in the C parameter with the +by combining the filename stems list passed in the C parameter with the potential filename extensions from each loader, which you can check with the C classmethod described below. Once this list of possible filenames is built it is treated exactly as in C above, as which it takes the same @@ -194,12 +192,16 @@ sub _load { for my $loader ( @try_plugins ) { next unless $loader->is_supported; $supported = 1; - my @configs - = eval { $loader->load( $filename, $loader_args{ $loader } ); }; + my @configs; + my $err = do { + local $@; + @configs = eval { $loader->load( $filename, $loader_args{ $loader } ); }; + $@; + }; # fatal error if we used extension matching - croak "Error parsing $filename: $@" if $@ and $use_ext_lut; - next if $@ or !@configs; + croak "Error parsing $filename: $err" if $err and $use_ext_lut; + next if $err or !@configs; # post-process config with a filter callback if ( $args->{ filter } ) { @@ -241,7 +243,7 @@ sub _support_error { =head2 finder( ) -The C classmethod returns the +The C classmethod returns the L object which is used to load the plugins. See the documentation for that module for more information. @@ -260,7 +262,7 @@ sub finder { =head2 plugins( ) -The C classmethod returns the names of configuration loading plugins as +The C classmethod returns the names of configuration loading plugins as found by L. =cut @@ -310,7 +312,7 @@ Config::Any requires no configuration files or environment variables. =head1 DEPENDENCIES -L +L And at least one of the following: L @@ -331,15 +333,15 @@ No bugs have been reported. Please report any bugs or feature requests to C, or through the web interface at -L. +L. =head1 AUTHOR -Joel Bernstein Erataxis@cpan.orgE +Joel Bernstein =head1 CONTRIBUTORS -This module was based on the original +This module was based on the original L module by Brian Cassidy C<< >>. @@ -380,7 +382,7 @@ SUCH DAMAGES. =head1 SEE ALSO -L +L -- now a wrapper around this module. =cut