develooper Front page | perl.perl5.porters | Postings from May 2003

Re: revisting perlio callback tab requirements

Thread Previous | Thread Next
Stas Bekman
May 11, 2003 00:41
Re: revisting perlio callback tab requirements
Message ID:
Nick Ing-Simmons wrote:
> Stas Bekman <> writes:
>>Regarding the problem of perl, not exporting PerlIOBase_* symbols, any ideas 
>>of what I can do to resolve this problem for mod_perl 2.0 on win32 and aix 
>>(and probably other systems, which use an explicit exports lists).
>>Here is the PerlIO tab that I use:
>>static PerlIO_funcs PerlIO_APR = {
>>    PerlIOBase_popped,
>>    PerlIOBase_binmode,         /* binmode() is handled by :crlf */
>>    PerlIOBase_unread,
>>    PerlIOBase_noop_fail,       /* fill */
>>    PerlIOBase_error,
>>    PerlIOBase_clearerr,
>>    PerlIOBase_setlinebuf,
> The symbols exported by perl are determined by 
> There is a hunk that starts:
> # Symbols that are the public face of the PerlIO layers implementation
> # These are in _addition to_ the public face of the abstraction
> # and need to be exported to allow XS modules to implement layers
> my @layer_syms = qw(
> 			 PerlIOBase_clearerr
> ...
> Which lists the PerlIO symbols that get exported.
> Looks like only one you are using which is missing is PerlIOBase_noop_fail.

Cool. So will that be fixed in 5.8.1/5.9.0?

> So I _think_ all you need to do is add that symbol to the list.

To which list? I can't mess with perl's export list, when building mod_perl, 
if you are referring to it. Is it safe to just copy the function and give it 
another name?

Thank you, Nick!

Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker     mod_perl Guide --->

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About