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.
  • The name change alleviates my main concern, for whatever that's worth.

  • is what I use YAML for, this sounds like a great module for about 90% of my yaml needs.

    I'm converting any config files I need to being yaml, it's just one less thing I have to write (config file parser) and I'm liking it.
  • I will have to look into to simplifying the dependency chain of Test-YAML-Meta [cpan.org].

    • In fact following your naming, it may be appropriate to change the name of my distribution to Test-CPAN-Meta.

  • I am still not satisfied. For me the namespace was never a problem, as it reminded me of another markup language with a tiny counterpart, namely SVG and SVG-Tiny. And as "-" is not a valid character for a module name I found it quite natually that it is replaced by "::".

    What bothers me more is that I don't know what is YAML::Tiny supposed to parse. It is not yet specified. I think there should be a written spec first.

    And then further problems: the META.yml specification clearly says that META.yml should

    • Writing a spec for the format supported by YAML::Tiny seems like a sound idea, actually. Restricting META.yml to that subset of YAML, once written, sounds like a better choice to me than putting libsyck in the core. Dual-life modules are “interesting” enough without throwing XS into the mix.

    • There is a LOT more resistance to having significant third-party C libraries in the core, compared to what I've done.

      As for a YAML-Tiny spec, I'll try to knock something up.