On 9/2/13 5:36 PM, Robert Rothenberg wrote:
Thank you for your comments.
To answer various questions/suggestions/comments:
- It will be for rewriting Perl, exclusively, using PPI, with Perl-centric
rules, so "Code" is not an appropriate namespace. (I don't think the PPI
namespace is appropriate
Thank you for your comments.
To answer various questions/suggestions/comments:
- It will be for rewriting Perl, exclusively, using PPI, with Perl-centric
rules, so "Code" is not an appropriate namespace. (I don't think the PPI
namespace is appropriate, since in theory, it could use something else
Wait, what's wrong with Perl::Snorft? I mean, does Moose actually describe
what it does? Given the lack of precision concerns, creating a new term
seems *perfect*
:-)
David
On Aug 31, 2013 1:11 AM, "Robert Rothenberg" wrote:
> At $work, I've been writing scripts that use PPI to munge massive am
Hi,
On Saturday, August 31, 2013, Bill Ward wrote:
> Is it truly only ever going to work on Perl code? Mightn't it also be
> pluginnable to rewrite other kinds of files?
>
>
If it does, Code:: would be a better place. There is already Code::TidyAll.
Bye,
> On Friday, August 30, 2013, Shlomi Fi
Is it truly only ever going to work on Perl code? Mightn't it also be
pluginnable to rewrite other kinds of files?
On Friday, August 30, 2013, Shlomi Fish wrote:
> On Sat, 31 Aug 2013 06:11:03 +0100
> Robert Rothenberg > wrote:
>
> > At $work, I've been writing scripts that use PPI to munge massi
Robert Rothenberg writes:
> So what should it be called? I'm thinking Perl::Rewrite is the best
> name.
Hi Rob. Hope Yorkshire is treating you well.
Perl::Rewrite sounds reasonable to me.
> - Perl::Refactor - except "refactoring" has a technical meaning that I
> don't think applies
I think tha
On Sat, 31 Aug 2013 06:11:03 +0100
Robert Rothenberg wrote:
> At $work, I've been writing scripts that use PPI to munge massive amounts
> of legacy code. So far simple things like changing die/warn to croak/carp,
> ensuring all modules specify a minimum version number, or changing print
> "foo\n"
At $work, I've been writing scripts that use PPI to munge massive amounts
of legacy code. So far simple things like changing die/warn to croak/carp,
ensuring all modules specify a minimum version number, or changing print
"foo\n" so say "foo", etc. It seems worthy enough to turn this code into a
CP
