Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Alias (5735)

  (email not shown publicly)

Journal of Alias (5735)

Thursday June 16, 2005
06:07 AM

How I wrote a refactoring Perl editor in 4 hours

[ #25231 ]
After finishing the shiny new PPI::Transform API, I figured why not convert Perl::Squish over to it, since that what inspired PPI::Transform in the first place.

So this afternoon, I decided I might have a very quick look at the PCE editor, and see what might be involved in adding PPI::Transform support to it.

The coolest thing about PCE is that it is just Perl. Not packaged into some hideous zipped/munged PAR-like thing, but completed open and raw .pm files. NEAT!

So after fiddling with it for 3 or 4 hours I can run a menu command that modifies the content of the document. :)

And another 10 lines of code makes that modification process work with any PPI::Transform-compatible class.

So now, I can do stuff like this!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Is that your creation as well or are you modifying another?
    • No, the PCE editor is the work of others. But it's not what you would call a "refactoring editor". And now it is! I call it IntelliPerl Lite :)
  • Is the source available? There is no mention of it that I can see on
    • There are two "PCE"s. One is an fairly simple and ugly editor written in I presume C.

      The other is more accurately known as "Proton CE" for now, and will be getting a better and less confusing name.

      The source, and specifically my hacks to it, are evil and unstable.

      I'm hoping to having something more stable and reliable by the time OSCON rolls around. Keeps your eyes peeled for more information.