Hi,
While I am about to adapt Embperl to Perl 5.14.x, I have found a problem with
Embperl and mod_perl 2.0.5.
When an Emberl script is called from mod_perl registrty script, Embperl use the
STDOUT/IN that mod_perl already has setup.
Until recently STDOUT etc. were tied filehandles and Embperl
On Friday, 05 August 2011 09:58:44 rich...@ecos.de wrote:
> Until recently STDOUT etc. were tied filehandles and Embperl XS code
> simply has grabbed the filehandle that was attached with Perl's
> magic.
Since perl 5.8.[12] or so perlio is standard. Since 5.8.6 stdio is
officially not supported a
Hi,
thanks for the quick feedback.
>
> The commit in question is 932875. The functions to do the above are
> C and
> C in
> F.
>
> They use C to get the handle.
>
[[GR]] I tried this already but I don't know how to convert the result into
something that I can pass to PerlIO_write as first ar
On Friday, 05 August 2011 11:51:59 rich...@ecos.de wrote:
> [[GR]] I tried this already but I don't know how to convert the result
> into something that I can pass to PerlIO_write as first argument.
> Also simply using PerlIO_stdout () as first argument doesn't work
> (this still goes to the real s
Hi,
>
> PerlIO *fp;
> if (!(fp = IoOFP(GvIOn(gv_fetchpv("STDOUT", GV_ADD, SVt_PVIO) {
> # bad handle
> # check perhaps if IoIFP returns something. If so, the handle is
> # read-only. To get an fp for reading us IoIFP.
> }
> PerlIO_write(fp, ...)
>
[[GR]] This works :-)
>
> Please
