Bug #77875 for YAML-Tiny: Would like to be able to pass IO::File handles to Dump/LoadFile

Mon Jun 18 02:31:49 2012 daniel.carosone [...] gmail.com - Ticket created

Subject:	Would like to be able to pass IO::File handles to Dump/LoadFile
Date:	Mon, 18 Jun 2012 16:31:39 +1000
To:	bugs-yaml-tiny [...] rt.cpan.org
From:	Daniel Carosone <daniel.carosone [...] gmail.com>

It would be nice to be able to pass an io handle to LoadFile/Dumpfile, rather than just a string filename. Obvious use case would be layered gzip compression, though Archive::Zip::MemberRead and many others might also be useful. The alternative is passing a content string fetched already to read_string. There's no saving of efficiency since that's what read does internally anyway, but it would make for much neater calling code to just be able to pass the handle. The write() function looks like it might just work passing a ":layer filename" string, because it concat's "<" onto the start for a 2-argument open. The read() function does a bunch of -f tests on the passed string which defeat attempts to pass a 2-argument open string. I haven't actually tried this trick with write, mostly because I want it more for LoadFile and IO:Uncompress:AnyUncompress with transparent (to not care whether i have manually gzip'd the files), and it won't work there. A very-low priority wishlist item, but: I notice some other comments about utf8 encoding, and wonder whether the solution to those doesn't also involve allowing it to use perlio layers. -- Dan.

Sat Sep 28 23:32:38 2013 dagolden [...] cpan.org - Correspondence added

On Mon Jun 18 02:31:49 2012, daniel.carosone@gmail.com wrote: Show quoted text

> It would be nice to be able to pass an io handle to LoadFile/Dumpfile, > rather than just a string filename. Obvious use case would be layered gzip > compression, though Archive::Zip::MemberRead and many others might also be > useful.

I think the wisdom of this depends a lot on whether Dump/Load continue to deal with characters (as YAML.pm does) or change to deal with UTF-8 encoded octets (as YAML::XS does). See https://rt.cpan.org/Ticket/Display.html?id=76180 for more on that. If this does get implemented, I wonder if it's possible to check the layers for correct encoding support (or raw mode). Or the function should binmode the handle itself for what is needed.

Sat Sep 28 23:32:38 2013 The RT System itself - Status changed from 'new' to 'open'

Sat Sep 28 23:33:12 2013 dagolden [...] cpan.org - Reference to ticket #76180 added

Fri Oct 25 05:40:20 2013 dagolden [...] cpan.org - Correspondence added

On reflection, this isn't something that YAML::Tiny will implement independently of the rest of the YAML ecosystem. And YAML::Tiny doesn't stream, so there's no advantage over just calling read_string or write_string and using the results with your own handle. Closing this ticket.

Fri Oct 25 05:40:21 2013 dagolden [...] cpan.org - Status changed from 'open' to 'resolved'