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

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.
  • This leads to the principle that wherever possible you should implement your software language tools in the same language as the one the tools works on.

    I quite see how your argument leads to that.

  • I want Padre to be SO good at working with Perl, and SO good at helping you impose your will on your code, that you'll hate your general purpose editor for not being good enough and making you change.

    Interpreting that this way [], I would like to change... my editor so that it can use Padre's features. Ideally(?) replacing the whole or parts of the PerlySense Perl backend.

    For that to happen, Padre needs to be designed so that the "editor" part is fairly cleanly separated from the "Perl aware IDE" parts (which

    • Just because I want Padre to rock isn't an excuse for not building it in a modular form, so that logical functionality can't be reused.

      So yes, wherever possible things are being implemented in a standalone fashion, so that at least other Perl editors can reuse the logic.

      For example, the debugger integration that Gabor wrote is quite likely going to appear in Kephra as well.

      • Which is good, because while you hope to make Padre so good that I’ll hate Vim for not being Padre, I already know with near-certainty that I’m going to hate Padre for not being Vim. :-) For sheer economy of motion, the Vim editing model is hard to beat.

        (It’s also wired deep into my muscle memory now. I constantly do things like hit [Esc] or type dd or such into HTML textareas or Gaim or anywhere else I edit text. I would try to :wq shells before I got ZZ and Ctrl-D wired into my fingers.)