Scott Scecina wrote:
Stas, you were right on the money. I had apr/apr-util 0.9.5 (and
1.0)built and installed separately and had been building against that.
When I built Apache and let it use it's own apr/apr-util everything was
fine. Since I also have subversion, I had hoped to use a common apr
I need to process and output data delivered via a webbrowser using the
CGI-interface.
To deal with "real" unicode-data I set the whole STDIN and STDOUT to
utf8 with binmode (as recommended at
http://www.perldoc.com/perl5.8.0/pod/perluniintro.html. My script would
not work otherwise)
While this
peter pilsl wrote:
I need to process and output data delivered via a webbrowser using the
CGI-interface.
To deal with "real" unicode-data I set the whole STDIN and STDOUT to
utf8 with binmode (as recommended at
http://www.perldoc.com/perl5.8.0/pod/perluniintro.html. My script would
not work oth
Markus Wichitill wrote:
peter pilsl wrote:
I need to process and output data delivered via a webbrowser using the
CGI-interface.
To deal with "real" unicode-data I set the whole STDIN and STDOUT to
utf8 with binmode (as recommended at
http://www.perldoc.com/perl5.8.0/pod/perluniintro.html. My sc
Stas Bekman wrote:
STDIN is not used with mod_perl.
It depends on how you write your program. When you don't qualify your
read and print calls with $r, then you do use STDIN, though mod_perl
overrides it, and does the qualified $r->read() calls behind the scenes
(via the perlio layer), but esse
Hi Lincoln,
under perl 5.6.1 CGI.pm (3.05 and earlier) produces tons of warnings in
this code:
CGI.pm:32226: my $seqno = unpack("%16C*",join('',localtime,values %ENV));
Apparently under perl 5.6 there could be %ENV entries which the key, but
undef as a value. Here is the fix:
--- CGI.pm 20
