In addition to my own modules, I've used it on Perl::Critic and PPI and
(aside from Adam Kennedy's weird Aussie spelling!) and it worked great.
That's about 29,000 lines of well-documented code -- I'm not sure if you
consider that large or not. Perl::Critic currently has 29 stopwords not
incl
On Oct 4, 2006, at 3:29 PM, Ovid wrote:
--- Ivan Tubert-Brohman <[EMAIL PROTECTED]> wrote:
Have you tried Pod::Spell and Test::Spelling? I think they already do
that.
I've tried Test::Spelling only to discover that there are so many
exceptions which it doesn't recognize that it was very pain
On Wednesday 04 October 2006 20:36, Ivan Tubert-Brohman wrote:
> I couldn't resist the temptation and started working on this feature.
> It's almost done now, I think it should be up by tomorrow or Friday.
No one has said this in a while, so:
Thank you! Great work!
-- c
Chris Dolan wrote:
On Oct 3, 2006, at 11:04 PM, Adam Kennedy wrote:
I'd ideally like to keep this constrained to a single environment
variable.
These tests are all the same sort of thing, tests that you run before
you release, but not otherwise. If so, there's the existing
AUTOMATED_TESTING
Ovid wrote:
> --- Ivan Tubert-Brohman <[EMAIL PROTECTED]> wrote:
>> Have you tried Pod::Spell and Test::Spelling? I think they already do
>> that.
>
> I've tried Test::Spelling only to discover that there are so many
> exceptions which it doesn't recognize that it was very painful to try
> and inc
--- Ivan Tubert-Brohman <[EMAIL PROTECTED]> wrote:
>
> Have you tried Pod::Spell and Test::Spelling? I think they already do
> that.
I've tried Test::Spelling only to discover that there are so many
exceptions which it doesn't recognize that it was very painful to try
and include in a test suite.
brian d foy wrote:
"Even better would be something like Pod::Spellchecker. I've started the
project several times but never had that much motivation to finish it.
Things would be simple if it could just spell-check everything, but I
want it to be able to skip verbatim blocks, things in C<>, and s
On Oct 3, 2006, at 3:58 PM, brian d foy wrote:
Even better would be something like Pod::Spellchecker. I've started
the
project several times but never had that much motivation to finish it.
Things would be simple if it could just spell-check everything, but I
want it to be able to skip verbati
I think this thread is headed towards completely over-engineering this.
For those who really want to customize what gets run when, I think brian's
Test::Manifest solution looks like a winner.
WIth environment variables, I prefer simplicity:
* AUTOMATED_TESTING -- signals that it's *unattended*,
On 10/3/06, chromatic <[EMAIL PROTECTED]> wrote:
I read a lot of documentation for CPAN modules and find a fair few typos. Yet
making patches for the POD is a hassle; I would have to download the archive,
uncompress it, copy the file, fix the typo, generate a patch, and submit it.
Wouldn't it b
In article <[EMAIL PROTECTED]>, chromatic
<[EMAIL PROTECTED]> wrote:
> Wouldn't it be nice to be able to pull up a text entry box online with the
> contents of the POD, fix any typos inline, then submit it to the server which
> can generate a patch and perhaps redirect me to rt.cpan.org? I thin
In article <[EMAIL PROTECTED]>, Chris
Dolan <[EMAIL PROTECTED]> wrote:
> On Oct 3, 2006, at 11:13 AM, David Golden wrote:
>
> > Given what you use, perhaps qr/AUTHOR_TEST/ is a good idea.
>
> That's cool. Then I could do C
> in my .t files and just set that to 1 in my .cshrc for all time.
I
12 matches
Mail list logo
