Re: Discuss change of namespace Test::Builder2 -> TB2?

On 11/15/11 8:40 AM, Leon Timmermans wrote: I'm not seeing the point really. By this logic we can reduce all frameworks on CPAN to some three letter acronym. To be honest I don't think Test::Builder is used directly often enough to justify that. I'm against abbreviation; it makes things harder

Re: standard for internal-only tests?

David Cantrell wrote: On Fri, Jul 31, 2009 at 10:51:57AM -0700, Jonathan Swartz wrote: Is there a standard for signifying internal-only tests, and for make test to figure out when they should run? The normal way is to have them skip unless some magic environment variable is set. Perl::Criti

Re: Should META.yml go in the repository?

David E. Wheeler wrote: This all built up over years as I tried to automate away each stupid distribution packaging mistake I've made in releasing something to CPAN. This should be a module. I'd use it. What about foy's Module::Release?

Re: Preparing a new Test::* module

Randy J. Ray wrote: On Sun, Apr 6, 2008 at 6:18 PM, Elliot Shank <[EMAIL PROTECTED]> wrote: Test::Text::Format (generic interface) Test::Text::Format::XML Test::Text::Format::YAML Test::Text::Format::Etcetera Feels a bit clumsy. I tend to dislike starting out three levels deep unle

Re: Preparing a new Test::* module

Randy J. Ray wrote: One thing I would like advice on (besides suggestions for future features), is, errr, the name. Right now, I'm leaning towards Test::Markup. That might wind up the YAML guys a bit, though (which is actually a quite-acceptable bonus to me), possibly the JSON camp as well. So I

A thank you to all CPAN testers.

Perl::Critic 1.082 wouldn't be what it is without you.

Re: Find all the modules 'use'd in a directory

Ovid wrote: But I can't tell how they're different other than that mine has documentation. I looked at it before starting. Yours is restricted to text in code: comments, strings, etc. I've been using mine at work for precisely the reason that started this thread: finding include statements

Re: Find all the modules 'use'd in a directory

Elliot Shank wrote: Matisse Enzer wrote: I want to utility program that I can point at a list of files and/r directories and get back a list of all the unique modules/pragmas that are imported via 'use' Before i write my own, using PPI, does this exist already in the CPAN? One

Re: Find all the modules 'use'd in a directory

Matisse Enzer wrote: I want to utility program that I can point at a list of files and/r directories and get back a list of all the unique modules/pragmas that are imported via 'use' Before i write my own, using PPI, does this exist already in the CPAN? One is already in progress. Right now

Re: Auto: Your message 'FAIL IO-AIO-2.51 i386-freebsd-thread-multi 6.2-release' has NOT been received

Jonathan Rockway wrote: Anyway, I think most authors like the reports. Personally, it motivates me to fix my modules when I know someone is actually trying to use them. (Smokers are nice too because I can fix my modules before a real person wastes their time trying to install my broken code :)