Doug MacEachern wrote: > On Tue, 18 Dec 2001, Stas Bekman wrote: > > correction from my last message: 4 bytes is a 32 bit int > > >>So is this a p5p call? >> > > i doubt p5p would go for it, but if you want to ask, go for it.
I can I'll ask while following up on my bug report. > we can work around it, even for Apache::PerlIO. we can generate a > modperl_largefile.h that defines the ripped out largefile flags, #include > that in apr_perlio.c then for Apache::PerlIO, just have two .c files, one > that implements all the PerlIO table functions (like apr_perlio.c) and one > that dereferences the request_rec when needed (without largefile flags > enable). So shell we put your last temp patch in before we get this done, and turn the todo sub-test normal? Or should we just get the ground ready for Apache::PerlIO? Also what happens if we want to use some of the perlio features in core? using the optional functions won't help if the .so wasn't loaded. Is there a way to make PerlIO a part of the core library, while it can be still used without modperl? I guess that's one of the linker solutions you've proposed when I've originally asked about how to use perlio in Apache::SubProcess. _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
