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.
  • Until your post, I'd never discovered the part of the specification that isn't shown in the actual specification that describes those special strings, so I'd never known to implement them.

    2 hours later, it's now fixed. YAML::Tiny will always quote the strings listed in those secondary type specifications.

    BTW, it's not case insensitive.

    It's apparently ( $str eq uc($str) or $str eq lc($str) or $str eq ucfirst($str) )

    Still ugh though.

    • I'll be you'll break a lot of code with this. I've previously worked with a module (can't recall, but I think it was SOAP related) which was guessing my data types and silently converting things for me. No end of headaches :(

      I didn't report this to you because I assumed you had deliberately kept things simple :)

      • The YAML-Tiny language specification does not contain support for these strings, and so the PARSER half of YAML::Tiny (and thus Parse::CPAN::Meta) will not support it.

        However, in emitting YAML it's quite appropriate that I make sure to avoid causing problems for others.

        So all I'm doing is detecting that the emitted string in a hash or array is one of these magic strings, and then escaping them (when I previously wasn't).