2.10 - added -StrictVars documentation section to the POD,

which was missing.

         - fixed a formatting error in the POD documentation.


git-svn-id: http://dev.catalyst.perl.org/repos/Config-General/trunk@36 be1acefe-a474-0410-9a34-9b3221f2030f

Changelog

@@ -1,3 +1,8 @@
+ 2.10    - added -StrictVars documentation section to the POD,
+	   which was missing.
+
+         - fixed a formatting error in the POD documentation.
+
  2.09    - added bugfix in '#' comment parsing. If current state
 	   was within a block, then /^   #/ was not ignored as
 	   comment but instead added as variable. Reported by

General.pm

@@ -17,7 +17,7 @@ use strict;
 use Carp;
 use Exporter;
 
-$Config::General::VERSION = "2.09";
+$Config::General::VERSION = "2.10";
 
 use vars  qw(@ISA @EXPORT);
 @ISA    = qw(Exporter);
@@ -1131,11 +1131,18 @@ access the parsed config. See L<Config::General::Extended> for more informations
 =item B<-StrictObjects>
 
 By default this is turned on, which causes Config::General to croak with an
-error if you try to access a non-existent key using the oop-way (B<-ExtendedAcess
+error if you try to access a non-existent key using the oop-way (B<-ExtendedAcess>
 enabled). If you turn B<-StrictObjects> off (by setting to 0 or "no") it will
 just return an empty object/hash/scalar. This is valid for OOP-access 8via AUTOLOAD
 and for the methods obj(), hash() and value().
 
+
+=item B<-StrictVars>
+
+By default this is turned on, which causes Config::General to croak with an
+error if an undefined variable with B<InterPolateVars> turned on occurs
+in a config. Set to I<false> (i.e. 0) to avoid such error messages.
+
 =item B<-SplitPolicy>
 
 You can influence the way how Config::General decides which part of a line
@@ -1707,7 +1714,7 @@ Thomas Linden <tom@daemon.de>
 
 =head1 VERSION
 
-2.09
+2.10
 
 =cut
 

README

@@ -103,4 +103,4 @@ AUTHOR
 
 
 VERSION
-	2.08
+	2.10