Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I have given this already some thoughts here: http://use.perl.org/~RGiersig/journal/34370/ [perl.org]

    What I came up with is a stream of yaml docs (separated by '---'), each containing a hash with info about that version. The reason to use a stream of separate docs is to cut back on indentation ("chrome"). So we only have one indentation level for the lists which means we can easily correct the format if somebody forgets to put the two spaces before the '- ' list token.

    Below is an example of how a Changes.yml could loo
    • I've seen your proposal and also thought about it.

      It seems a bit too detailed. Also I don't think that splitting the structure into different YAML streams for the sake of indentation is ideal. I don't mind indentation - after all, it's supposed to be machine-readable.

      If you really want a human-readable version as well, just have the YAML in Changes.yml and run:

      changes -f Changes.yml -ff >Changes

      By the way, more updates are coming. I've simplified the YAML somewhat (less indentation!) and added a YAML validator that uses a schema with Kwalify.pm. v0.04 should be on CPAN soon.