Curtis Poe wrote:
>
> Ann Barcomb (kudra on perlmonks.org) reported a problem with CGI.pm
> where data read from STDIN was not tainted. See
> http://www.perlmonks.org/index.pl?node_id=168090
>
> The problem was traced to shellwords.pl using regexes to parse the
> data.
> The following patch wil
Dan the Encode Maintainer wrote:
!-ST(0) = &PL_sv_no;
!+/* ST(0) = &PL_sv_no; */
!+ST(0) = &PL_sv_yes;
! XSRETURN(1);
! }
!
!Even if it works, I do not consider this to be a radical cure. But a
!cure nonetheless
!
!BTW, what is the most concise way to check the architectur
At 05:54 PM 5/21/2002 +0100, Nick Ing-Simmons wrote:
>Nicholas Clark <[EMAIL PROTECTED]> writes:
>>What do you mean multiple ungetc?
>>If that's going to stdio, ANSI only guarantee that the first ungetc will
>>succeed.
>
>I know that. ANSI C does not allow you to snoop the buffer either but we
>
