Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the YAML CPAN distribution.

Report information
The Basics
Id: 41463
Status: resolved
Priority: 0/
Queue: YAML

People
Owner: Nobody in particular
Requestors: ribasushi [...] leporine.io
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: (no value)
Fixed in: (no value)



Subject: Objects do not round trip properly between YAML and YAML::XS
The Load() of both YAML and YAML::XS throw exceptions when confronted with a dump produced by the other module. Please run the attached test script to witness the problem first hand.
Subject: yaml.test
Download yaml.test
application/octet-stream 706b

Message body not shown because it is not plain text.

The attached YAML is well-formed and is accepted by YAML but not by YAML::XS which fails with: <pre> YAML::XS::Load Error: The problem: Control characters are not allowed was found at document: 0 </pre> on Perl 5.8.8 on a 64-bit Intel quad core running Fedora Core 7. It was created by YAML. I believe this may be something to do with utf8 encoding. SSF
--- DB00028: MSDS_Files: Not Available Mass_Spec_File: 0 Mechanism_Of_Action: 'Antibodies prevent infection by attaching to the surface of invading pathogens and aiding in their disposal before they can infect cells. Antibodies remove pathogens via complement activation, agglutination or precipitation, pathogen receptor blocking, macrophage “tagging” or neutralization (via binding) of pathogen toxins.' Melting_Point: '61 oC (FAB fragment), 71 oC (whole mAb) - Vermeer, A.W.P. & Norde, W., Biophys. J. 78:394-404 (2000).' Molecular_Weight_Avg: 142682.3
Poke-poke? The attached test (yaml.test) still fails with latest YAML 0.84. I sadly do not know enough XS to figure it out :(
This issue has been copied to: https://github.com/ingydotnet/yaml-pm/issues/92 please take all future correspondence there. This ticket will remain open but please do not reply here. This ticket will be closed when the github issue is dealt with.
Finally fixed in 1.25_001