| Subject: | various problems with 0.0.4 |
| Date: | Fri, 26 Jan 2007 13:09:27 +0100 |
| To: | <bug-Config-Std [...] rt.cpan.org> |
| From: | <Norman.Azadian [...] swisscom.com> |
Message body not shown because it is not plain text.
Message body not shown because it is not plain text.
Message body not shown because it is not plain text.
I love the design of this module, but there are still a few rough edges
in the current version:
- Running the manpage example and dumping the output with Data::Dumper,
the result is different that what the manpage shows. This is confusing,
and should be explained in the documentation.
- Speaking of documentation, it appears that defining def_sep silently
fails unless it is one of ':' or '='. This obviously at least needs to
be documented.
- It appears that, for multi-valued items, the output separator for a
new line depends entirely on what was used on the previous line, no
matter if def_sep is set or not. This only seems to be true if the
previous line has a non-empty value.
- Initial comments, followed by a blank line and then a section,
disappear when the configuration is written. This seems to be a
function of the output, not the input. If, for example, a new item is
inserted in the '' section, then the leading comments will be output as
expected.
FWIW, like another commentator, I find it annoying that a multi-value
item which currently only has one value is just a scalar. This uglifies
the application code considerably. One possible improvement would be to
define yet another separator, e.g., :=, for multi-value items. This
would have the additional advantage of making the configuration file
somewhat more self-documenting.
<<t3>> <<t3.in>> <<t3.out>>
NHA
---
Norman H. Azadian FX-FWS-IT-PJE-FOP-FOA-CST
Swisscom AG Zentweg 9 CH-3006 Ostermundigen
+41 31 342 2271 norman.azadian@swisscom.com
<mailto:norman@azadian.ch>