On Mon, Sep 13, 2010 at 10:27 AM, Oliver Trosien <o.tros...@epages.com> wrote: > Hello Padre-Dev, > > > > I’d like to say hello and ask for your suggestions to a feature I’m > discussing > > with the developers of Perl::Critic. It is about adding refactoring > possibilities to > > perlcritic [1]. There are many good rules out there and most of them have > > an easy fix, which the programmer currently has to code manually. > > > > As padre has the ambitious goal of refactoring perl, why not take > > the chance and create some kind of connection between perlcritic and padre. > > > > What I’m asking you to do is, join the discussion on cpan and give your > input, > > so the design of the feature will be in a way that’s useable for padre. > > > > Regards, > > Oliver > > > > [1] https://rt.cpan.org/Public/Bug/Display.html?id=60801
Thanks for the pointer. I also think that such refactoring tool should be separate from Perl::Critic and it should not be totally automatic. Before each change I'd like to approve/reject it. Maybe fine tune it before accepting it or telling to tool to inject a "non-violation" mark of Perl::Critic so it won't complain about it next time. This tool might need to have some cooperation with the developers of Perl::Critic as it might need a better API that what Perl::Critic currently provides but as I am not too familiar with it I don't really know. I'd really like to see this integrated into Padre or rather into the Perl::Critic plugin of Padre. Gabor _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
