develooper Front page | perl.perl5.porters | Postings from July 2011

Re: How much of PerlIO is part of the API?

Thread Previous | Thread Next
From:
Nicholas Clark
Date:
July 4, 2011 06:47
Subject:
Re: How much of PerlIO is part of the API?
Message ID:
20110704134737.GV23881@plum.flirble.org
On Mon, Jul 04, 2011 at 02:41:38PM +0200, Leon Timmermans wrote:
> Currently, a small part of PerlIO is documented, declared API and
> exported. This is pretty much only the end-user functionality
> equivalent to what stdio provides. However, most of PerlIO is entirely
> undocumented and not declared part of the API anywhere, but is
> exported regardless. This are the interfaces used to define PerlIO
> layers.
> 
> I think this is rather problematic and that I they should be made part
> of the official API, but I would prefer them to be changed slightly:
> they currently require the end user to pass aTHX_ explicitly. Changing
> this however will break PerlIO modules on CPAN that use these
> interfaces.

You mean the functions currently defined in perlio.h, such as

PERL_EXPORT_C int PerlIO_apply_layera(pTHX_ PerlIO *f, const char *mode,
		    PerlIO_list_t *layers, IV n, IV max);


If so, could you give an example of what you're proposing that the source code
interface should be?


PerlIO is a mess, and I'd hate to make the mess worse before we get a chance
to make it better.

Nicholas Clark

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About