use Perl

• perlcritic-fly.el???? (Score:1)

  by jjore (6662)

  I want this. I *so* want this. The thing that bothers me is that I'd like to do some sane defaults for @INC because it becomes very difficult to validate modules or things using modules that aren't installed by the ambient or shebang perl.
  
  I'm thinking that just autoadding lib/, t/, uh... t/lib would be spiffy. Perhaps with some dwimmery to notice if those directories can be found by navigating up the directory tree:
  
      ~jjore/src/Foo-Bar/t$ ... # automatically find ../lib
  
  Maybe there oughta be som
  • Re:perlcritic-fly.el???? (Score:1)

    by thaljef (6477) on 2006.11.16 22:45 (#51693) Homepage

    I downloaded flymake.el from their repository, but I wasn't able to make it work with my Emacs 21.2.1. I don't have the lisp-fu to figure it out, so I'll probably just wait until Emacs 22 is released.

    Putting aside the argument about compiling untrusted code, you should be able to get the effect you want by putting "use criticism;" at the top of your script. In the latest release of criticism.pm, we changed the default output format to look exactly like the perl's native compiler warnings. So when you run "perl -c SomeFile.pm" the Perl::Critic warnings blend right into the compiler warnings. For a while, this was how the EPIC guys were integrating with Perl::Critic.

    If you're able to get flymake-mode working, please let me know if the "use criticism;" trick actually works.

    -Jeff

    Reply to This

    Parent

    • Re: (Score:1)

      by jjore (6662)

      Ok... but `use criticism' only works when you run the code.
      • Re: (Score:1)

        by thaljef (6477)

        Not so. It is pragma-like, so it executes when you compile the code. Observe what happens when you say "perl -c" on a file with "use criticism;"

        -Jeff
        • Re: (Score:1)

          by jjore (6662)

          Well yeah, that's what I said. -c is a form of running the code.
          • Re: (Score:1)

            by thaljef (6477)

            I thought that's what you were shooting for -- running perlcritic at compile time. But if not, then I understand. My apoligies.

            Perhaps we could repurpose the flymake code and just substitute "perlcritic" where it says "perl -c". But your lisp skills are far better than mine.

            -Jeff
            • Re: (Score:1)

              by jjore (6662)

              I thought you were proposing running perlcritic instead of perl -c + the criticism pragma. So it appears I was already at the endgame.