On Jan 01, 2004, at 12:32, Masanori HATA wrote:
Hello,
I have a simple question:
It seems that utf8::decode() does not work for
any tainted variables under the -T (Taint) mode.
Is it right?
Wrong.
What drove you to such a conclusion? It does work. Try something like
perl -T -le 'utf8::decod
Thanks for replying, Dan-san.
At 18:09 04/01/01 +0900, Dan wrote:
>>It seems that utf8::decode() does not work for
>>any tainted variables under the -T (Taint) mode.
>What drove you to such a conclusion? It does work. Try something like
>
> perl -T -le 'utf8::decode($ARGV[0])' something
>
>an
On Jan 01, 2004, at 21:49, Masanori HATA wrote:
Sorry, no. Since the case which I would like to suggest
seems not to be fatal. Perl would not die, but it would
take the tainted value as a Non-UTF8 string.
My sample code is like below (test.pl):
-
utf8
At 22:32 04/01/01 +0900, Dan wrote:
>Aha! I see your point at last. And I found your argument was correct.
Sorry my poor English and insufficient explanation. :)
>I am not sure how severe it is but this is a bug indeed.
Oh, indeed? I had almost believed that it was a featured behavior.
I hope
> On Wed, 31 Dec 2003 16:21:36 +0100, Eric Cholet <[EMAIL PROTECTED]> said:
> Can anyone enlighten me as to why \W behaves differently depending
> on wether it's inside or outside of a character class, for certain
> characters:
I have reported this as bug 18281
http://guest:[EMAIL PROT
Andreas J Koenig wrote in perl.unicode :
>> On Wed, 31 Dec 2003 16:21:36 +0100, Eric Cholet <[EMAIL PROTECTED]> said:
>
> > Can anyone enlighten me as to why \W behaves differently depending
> > on wether it's inside or outside of a character class, for certain
> > characters:
>
> I have r
Le 1 janv. 04, à 17:50, Rafael Garcia-Suarez a écrit :
+(However, and as a limitation of the current implementation, using
+C<\w> or C<\W> I a C<[...]> character class will still match
+with byte semantics.)
I don't think it applies to \w, only \W. \x{df} matches [\w] just fine,
as shown in Andrea
