NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
several minutes ago. We don't need no stinkin' tactical nukes.
(By the way, do you have change for 10 million people?) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
re: changes.conf (Score:1)
I don't see the value in the top-level section for version-date pairs. Presumably the file will always be written out to place the sections in a useful order, and anyone who wants to re-order the sections or deal with them logically will read them in, and can then sort by any field he likes, rather than needing a redundant index in the file.
INI files do not by default have good semantics for multi-value entries. While IniFiles might add it, that means that dealing with these files requires dealing with some bespoke data format. (Well, more bespoke than INI files are to begin with.) At least YAML has a spec and grammar, and multiple implementations across many languages.
Whatever super-awesome changelog format is used should be something that people can use outside of Perl. There *is* life out there.
rjbs
Reply to This
Re: (Score:1)
I would argue that a change log supplies config info pertaining to each version, so the choice is not that bad. But I'll certainly reconsider. After all, nothing is cast in Perl-based stone just yet.
I would like an extension which definitively indicated the format, a la yml and xml, but without the format being known, that's not so easy.
Changelog.ini is reasonable. That sort of feedback is the point of posting in the first place.
The date can easily be a per-section entry, and