Skip Menu |

Preferred bug tracker

Please email the preferred bug tracker to report your issue.

This queue is for tickets about the PPIx-Regexp CPAN distribution.

Report information
The Basics
Id: 85050
Status: resolved
Priority: 0/
Queue: PPIx-Regexp

People
Owner: Nobody in particular
Requestors: dsteinbrunner [...] pobox.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Spelling corrections
PPIx/Regexp/Token/Interpolation.pm 125: plausably -> plausibly PPIx/Regexp/Token/Literal.pm 100: documentaion -> documentation 142: uandle -> handle PPIx/Regexp/Tokenizer.pm 51: percieved -> perceived PPIx/Regexp.pm 428: regexp, whether explicitly or by the modifiers passed *in in* the This last one is pointing out the duplication of "in"
On Sat May 04 13:46:51 2013, dsteinbrunner@pobox.com wrote: Show quoted text
> PPIx/Regexp/Token/Interpolation.pm > 125: plausably -> plausibly > > PPIx/Regexp/Token/Literal.pm > 100: documentaion -> documentation > 142: uandle -> handle > > PPIx/Regexp/Tokenizer.pm > 51: percieved -> perceived > > PPIx/Regexp.pm > 428: regexp, whether explicitly or by the modifiers passed *in in* the > > This last one is pointing out the duplication of "in"
Thank you. Given that you read my comments as well as the POD, I'm surprised you did not find more. Unfortunately Test::Spelling does not look in comments, so in general they get fixed up only if I actually am in the code for some other reason and notice something glaring. The "in in" in the POD was also a good catch. Release 0.033_01 has gone to PAUSE, and should appear at your friendly neighborhood CPAN mirror Real Soon Now. Yes, a development release is probably overkill for spelling changes, but what the hey? Please check the credit to you in the Changes file and let me know if I should change something. I confess to inferring your name (perhaps wildly incorrectly) from your mailing address.
From: dsteinbrunner [...] pobox.com
On Sun May 05 12:28:46 2013, WYANT wrote: Show quoted text
> Thank you. Given that you read my comments as well as the POD, I'm > surprised you did not find more. Unfortunately Test::Spelling does > not look in comments, so in general they get fixed up only if I > actually am in the code for some other reason and notice something > glaring. > > The "in in" in the POD was also a good catch.
Well, I did not actually read the comments... I'm using my own process to check the spelling in pod and comments along with looking for duplication of words in those same places. Currently I'm just using this process against the modules I have installed on my system. Not sure where I'm going with this except for submitting bugs and patches for now. Show quoted text
> Release 0.033_01 has gone to PAUSE, and should appear at your friendly > neighborhood CPAN mirror Real Soon Now. Yes, a development release > is probably overkill for spelling changes, but what the hey? > > Please check the credit to you in the Changes file and let me know if > I should change something. I confess to inferring your name > (perhaps wildly incorrectly) from your mailing address.
David Steinbrunner or dsteinbrunner will work.
Version 0.034 having been out for about a week, I am marking this ticket resolved. Please let me know if there are any further issues.