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.
  • How can a module that's unable to say what it actually does ever have a bug?

    YAML::Tiny is a misnomer and should be abandoned unless it is intending to become compliant to the YAML spec.

    Did you ever answer http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2007-06/msg00783.html [mpe.mpg.de]
    ?
    • YAML.pm is not compliant with the YAML spec.

      YAML::Syck is not compliant with the YAML spec.

      There's a number of instances in YAML::Tiny's comparative tests where I've had to skip comparisons with those modules because they fail.

      YAML::Tiny is quite clear about what it is, a module that supports reading and writing of the block-mode JSON-subset of the YAML specification.
      • by srezic (8057) on 2007.12.06 12:46 (#59324) Journal
        At least YAML.pm and YAML::Syck are aiming to be compliant with the YAML spec. If I find a problem with one of these modules, I can look into a spec and decide if it's a bug and file a report. With YAML::Tiny it's difficult to tell whether it's intended or a bug.

        About the JSON-subset: where can I read this? I grepped the documentation and could not find a reference to it.

        I am not against a tiny implementation of YAML, but it should go together with a tiny spec.