Stories
Slash Boxes
Comments
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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Getting timely notices about significant developments is wonderful. But they all seem to assume that everyone knows what the hell the thing is. What. Is. It. Man!?!? (Sure, I guess I could go look, but then what's the point of advertising?)
    --
    The great thing about multitasking is that several things can go wrong at once.
    • Well, one click away from the journal entry is this description:

      PerlySense is a Perl IDE back-end that integrates with editor front-ends, currently Emacs.

      Conveniently navigate and browse the code and documentation of your project and Perl installation.

      Run tests and scripts and syntax check source with easy navigation to errors/warnings/failing tests.

      Highlight syntax errors, warnings and Perl::Critic complaints in the source while editing.
      • Your time must not be worth much.
        --
        The great thing about multitasking is that several things can go wrong at once.
        • ...says the guy who takes the extra time to be a dick to people who give him free stuff. I really don't get this.
          • I think that part of the point of getting such notices is that most people won't click through and when the description isn't there, then they just shrug and move on.
            When you want to get the message out to more people, it helps to put a bit more information up front.
  • I truly love it when people put effort into better IDE-like support for Perl. Right now I'm undecided as to getting my emacs environment beefed up (e.g. packing in stuff like PerlySense) or trying to like (or make) the Eclipse tools better. EPIC [sourceforge.net] does have some momentum ATM, it seems, thanks in large part to PPI [cpan.org]. Since it looks like PerlySense is built on PPI too, I hope some of that momentum transfers its way too.
    • I'm not 100% sure how EPIC does its thing (I looked into it briefly last time they announced a release to see how command completion was done), but I think it could take advantage of PerlySense to get the information it wants to display and use.

      That's the point of PerlySense being heavy on the Perl side and rather light on the Emacs side, to be able to reuse it across different front-ends (for example, I envision an HTML front-end to make it usable for a team regardless of editor preferences).