view release on metacpan or  search on metacpan

Changelog  view on Meta::CPAN

       cause weird results if the here-doc contained
       multiple <<XXX strings.
       this bug has been fixed by re-organizing the _read()
       method. now the parser is only active outside of
       here-docs.

     - here-doc parsing bug fixed, which ignored the
       -SplitPolicy settings completely, now it is aware
       of the split policy

 2.12    - fixed cpan bugid #1768, stuff inside a hash given
       by the -DefaultConfig parameter was ignored by
       the new interpolation code, this has been fixed.

     - fixed another bug in the new interpolation code,
       which made variable global, the variable scope
       were ignored. Now a special constructed hash
       exists, which makes sure, that variables only
       valid within its correct scope.

 2.11     - heavy change in the variable interpolation code.

Changelog  view on Meta::CPAN

     - applied patch by Matthias Pitzl <matthias@izb.net>, which    
       fixes a bug at parsing apache-like include directive
       (Include ...). It did not properly trim unnecessary whitespaces
       so that the filename to be included became invalid. This
       bug espessially occurred if one saved a hash containing
       a key/value pair like this: "Include" => "/etc/grs.cfg",
       which was then saved as "Include   /etc/grs.cfg", the
       parser returned "  /etc/grs.cfg" which, of course, does
       not exists. odd...

 2.07    - fixed cpan bugid #1351, SaveConfig contained a deprecated
           function call which caused the module to croak.
         - added feature request, if in extended mode (OOP turned
           on with -ExtendedAccess => 1 access to non-existent keys    
           caused a croak. While this is still the default behavior
           it is now possible to turn this off using -StrictObjects => 0.
         - added this to the related pod section in ::Extended.
         - fixed bug in new() which caused a couple of errors
           if the ConfigFile parameter is not set, or is set to
           undef. In this case it will now simply create an empty
           object.