mirror of
https://codeberg.org/scip/Config-General.git
synced 2025-12-16 20:21:01 +01:00
2ae16df3ad
- added code to check if unknown parameters to new() has been supplied. git-svn-id: http://dev.catalyst.perl.org/repos/Config-General/trunk@18 be1acefe-a474-0410-9a34-9b3221f2030f
94 lines
4.0 KiB
Plaintext
94 lines
4.0 KiB
Plaintext
1.30: - fixed typo, which made 1.29 unusable (undefined var %config)
|
|
- added code to check if unknown parameters to new()
|
|
has been supplied.
|
|
|
|
1.29:
|
|
- added 2 procedural functions ParseConf and SaveConf
|
|
- added new parameters -AutoTrue and -FlagBits
|
|
- added save_file() which replaces save(), which was
|
|
weird implemented. If the user only supplied a hash
|
|
as parameter to save(), then the first key was
|
|
used as the filename and the rest was used
|
|
as a config hash (which was then of an uneven size).
|
|
- save_file() takes now instead of a hash a hash-ref
|
|
and a filename. And the hashref is optional, since
|
|
the object already contains a complete hash.
|
|
- new method save_string() added, which returns the
|
|
ready generated string instead of writing it to
|
|
disk. The user can then save it himself.
|
|
- POD updated.
|
|
|
|
1.28:
|
|
- added contributed sub module Config::General::Interpolated
|
|
by "Wei-Hon Chen" <plasmaball@pchome.com.tw> with
|
|
help from "Autrijus Tang" <autrijus@autrijus.org>
|
|
which makes it possible to use variables inside
|
|
config files.
|
|
- _read() accepts now c-comments inside c-comments if
|
|
they are on a single line.
|
|
- _read() is now more tolerant to here-identifiers
|
|
(the ends of here-docs), whitespaces right after
|
|
such an identifier are allowed (i.e. "EOF ").
|
|
- _read() does now behave somewhat different with
|
|
C-comments, they will be the first thing being
|
|
processed in a config, so the parser really
|
|
ignores everything inside C-comments. Previously
|
|
it did not do that, for example here-docs has
|
|
not been ignored.
|
|
|
|
1.27: - "make test" complained about uninitialized value
|
|
in :146, which is now fixed.
|
|
|
|
1.26: - added filehandle capability to -file.
|
|
- added -String parameter to new(), which allows
|
|
one to supply the whole config as a string.
|
|
- added -MergeDuplicateBlocks option, which causes
|
|
duplicate blocks to be merged.
|
|
|
|
1.25: - include statements are now case insensitive
|
|
- include statements may now also being used with
|
|
indentation(leading and following whitespaces are
|
|
allowed)
|
|
- changed the end here-doc regexp from .+? to \S+?
|
|
so " <<include..." works as expected (this was a bug, imo)
|
|
- added new option -IncludeRelative (idea contributed
|
|
by Valerio_Valdez Paolini <paolini@students.cs.unibo.it>
|
|
and Anton Luht <luht@ank.ru> :-)
|
|
This allows to include files from the location of
|
|
the configfile instead from the working directory.
|
|
|
|
1.24: - AllowMultiOptions printed out the value and not the
|
|
option itself, if more than one of this particular
|
|
option occured.
|
|
- added -UseApacheInclude feature, contributed by
|
|
Thomas Klausner <domm@zsi.at>
|
|
- fixed bug with multiple options stuff, which did not
|
|
work with blocks or named blocks. Pointed out by
|
|
Thomas Klausner <domm@zsi.at>, who meant it being
|
|
feature request, but in fact it was a bug (IMHO).
|
|
- Config::General does now contain also it's OO-sister
|
|
Config::General::Extended, which is from now on
|
|
no more available as an extra module, because it
|
|
lived a shadowy existence.
|
|
- finally(!) created a Changelog file (this one, yes).
|
|
|
|
1.23: - fixed bug, which removed trailing or leading " even
|
|
no matching " was there.
|
|
|
|
1.22: - added a new option to new(): -LowerCaseNames, which
|
|
lowercases all option-names (feature request)
|
|
|
|
1.21: - lines with just one "#" became an option array named
|
|
"#" with empty entries, very weird, fixed
|
|
|
|
1.20: - added an if(exists... to new() for checking of the
|
|
existence of -AllowMultiOptions.
|
|
- use now "local $_" because it caused weird results
|
|
if a user used $_ with the module.
|
|
|
|
1.19: - you can escape "#" characters using a backslash: "\#"
|
|
which will now no more treated as a comment.
|
|
- comments inside here-documents will now remain in the
|
|
here-doc value.
|
|
|
|
previous history logs are lost in space :-( |