Re^4: Where are the Perl::Critic Unicode policies for the Camel?

Yes, you’re 100% right about all those things. Thanks for pointing them out, too.

My context was in the processing of text files, normally NLP type stuff but sometimes CSV files in this or that encoding.

I nevertheless think there are a lot of mistakes made, and that opening a textfile without specifying its encoding is a big problem.

I wonder what if anything can reasonably be done about that though.

--tom

Comment on Re^4: Where are the Perl::Critic Unicode policies for the Camel?

Replies are listed 'Best First'.
Re^5: Where are the Perl::Critic Unicode policies for the Camel? by vsespb (Chaplain) on Oct 06, 2013 at 22:52 UTC
What about writing wrapper library over text file operations - thus you can enforce encoding specification, and even maybe prohobit foreach (<INPUT>) by providing own iterator function. Same probably can be done for some common text operations And probably some typical regexps, character constant can be moved out, some wrappers can be written over regexp (i.e. functions which create regexp at runtime) Cases when you care about "\X" vs "." are probably limited - spliting text, determining visible length, maybe something else - can be moved out to library too	[reply]

Replies are listed 'Best First'.