Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Where are the Unicode P::C policies?Hm, do you think it's possible to implement any useful set of checks related to Unicode in static code analyzer? Afaik, perlcritic only checks one file, so it's impossible to say where data come from and if this text data or no. It's impossible to say if we have encoding layers for our file handles or no. Actually it's even impossible to tell at runtime if we have binary data or no, so it's probably even more hard to tell to static code analyzer. The thing I can think of is some warnings for regexps (like if we have "\d" in regexp it can mean something beyond 0-9, depending on flags (possible to analyze), 'use feature's (possible to analyze), data (impossible to analyze). In reply to Re: Where are the Perl::Critic policies for the Camel?
by vsespb
|
|