Re: Converting from Storable to YAML

[thezip]

in reply to Converting from Storable to YAML

Better still is to use JSON::XS.

use strict;
use warnings;
use JSON::XS;

my $hash {};

... fill up the hashref with stuff ...

my $json = JSON::XS->new()->pretty();

my $json_text = $json->encode($hash);

open(my $ofh, '>', $outfilename);
print $ofh $json_text;
close $ofh;

The stored format in the file is quite readable, and JSON::XS is uber-fast when compared to YAML and Storable.

[Your Mother]

JSON::XS--which I love--is harder to edit by hand, has less support for objects/etc, and is on par with Storable for speed. I think it can be faster for certain strings/sizes but I also recall Storable being better for others. Oh, and YAML::XS was not around when those benchmarks were done so it might well be on the same playing field since it's C beneath too.

So, I recommend it too but I tend to personally use it for machine cases and Ajax only, never for human edited configuration, etc.

[moritz]

JSON and YAML fill two different needs.

JSON is meant for data interchange between different languages, and can only handle the most basic data types (arrays, hashes, strings, numbers and undef, and only tree structures).

YAML on the other hand also handles blessed references and self-referential constructs (ie. arbitrary object graphs).

No wonder that JSON modules are faster than YAML modules, they do way less.

When the feature set of JSON is sufficient, choosing JSON over YAML is a good idea (simpler format, easier to implement right, less chance of ambiguity). If not, not.

There's also JSYNC, which tries to combine the advantages of both formats. I don't know how mature it is today.