Skip Menu |

This queue is for tickets about the Perl-Critic-More CPAN distribution.

Report information
The Basics
Id: 36895
Status: open
Priority: 0/
Queue: Perl-Critic-More
People
Owner: Nobody in particular
Requestors: user42 [...] zip.com.au
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Fri Jun 20 13:56:00 2008 user42 [...] zip.com.au - Ticket created
Subject: suggest RequireASCII allow non-ascii in comments
Date: Wed, 18 Jun 2008 10:46:46 +1000
To: bug-Perl-Critic-More [...] rt.cpan.org
From: Kevin Ryde <user42 [...] zip.com.au>
As a suggestion, maybe CodeLayout::RequireASCII could have an option to allow non-ascii in comments. I've got a couple of files with bizarre stuff in the comments, but where I'd like the code itself to be ascii. There's probably a few variations on the theme. Perhaps non-ascii is ok in the pod, perhaps it's ok in strings but not identifiers, maybe it's ok in regexps. I haven't thought through the possibilities, only that comments could be a fairly reasonable exception to start with.
  Tue Jun 16 06:00:11 2009 hasch-cpan [...] cozap.com - Correspondence added
Non-ASCII characters in source code introduce encoding issues, no matter for what purpose they are used. The point of a metric like RequireASCII is to tell you just that. I'd prefer to keep it that way. -Martin
  Tue Jun 16 06:00:12 2009 The RT System itself - Status changed from 'new' to 'open'