Front page | perl.perl5.porters |
Postings from January 2011
> 81fe74f Leon Timmermans <fawaka@gmail.com> -- Define PerlIOBase_open > > New PerlIO API. Shouldn't this also be documented in perlapi? The docs > in perliol.pod just say you can use it, but nothing says what its > prototype etc. are It's an implementation of the Open method, so the prototype is known. PerlIO in general is pretty much entirely absent from perlapi, and I think that's far more urgent to document end-user functions (e.g. PerlIO_open, PerlIO_read, etc…) than vtable function implementations. In fact I think it would be outright confusing to document it without documenting the main interface. That's a fairly big project that's somewhere on my todo list but unlikely to be done before 5.14. > c0888ac Leon Timmermans <fawaka@gmail.com> -- Use PerlIOBase_open > for pop, utf8 and bytes layers > > Does this change existing behavior? Yes, but only in cases where it previously didn't work. How about this perldelta entry: «Three of Perl's builtin PerlIO layers (C<:pop>, C<:utf8> and C<:bytes>) didn't allow stacking when opening a file. For example this: open FH, '>:pop:perlio', 'some.file' or die $!; Would throw an error: "Invalid argument". This has been fixed in this release» > ecfd064 Leon Timmermans <fawaka@gmail.com> -- Fixes 'raw' layer > for perl#80764 This fix exposes more of #38456, my fix for that probably should be applied along with it (AFAIK it hasn't), or else there's a previously mentioned regression on windows.Thread Previous | Thread Next