I solve this problem by writing unit tests. I start a Perl project with Module::Starter which provides the basis for your unit tests. 

jeffa@jeffa:~/code$ module-starter --module=Foo::Bar --author=me --ema
+il=me@here.com
Added to MANIFEST: Changes
Added to MANIFEST: ignore.txt
Added to MANIFEST: lib/Foo/Bar.pm
Added to MANIFEST: Makefile.PL
Added to MANIFEST: MANIFEST
Added to MANIFEST: README
Added to MANIFEST: t/00-load.t
Added to MANIFEST: t/manifest.t
Added to MANIFEST: t/pod-coverage.t
Added to MANIFEST: t/pod.t
Added to MANIFEST: xt/boilerplate.t
Created starter directories and files
jeffa@jeffa:~/code$ pushd Foo-Bar/
~/code/Foo-Bar ~/code
jeffa@jeffa:~/code/Foo-Bar$ prove -lr
./t/00-load.t ....... 1/? # Testing Foo::Bar 0.01, Perl 5.022001
./t/00-load.t ....... ok   
./t/manifest.t ...... skipped: Author tests not required for installat
+ion
./t/pod-coverage.t .. skipped: Author tests not required for installat
+ion
./t/pod.t ........... skipped: Author tests not required for installat
+ion
./xt/boilerplate.t .. ok   
All tests successful.
Files=5, Tests=4,  0 wallclock secs ( 0.02 usr  0.01 sys +  0.02 cusr 
+ 0.01 csys =  0.06 CPU)
Result: PASS

[download]
In my opinion, this is far better than a mere perl -c because you now have a framework with which to add finer grain tests for your code. Replace watch with a service like Jenkins or https://travis-ci.org and increase your available options.

For what it is worth, i have been using vim exclusively for over 15 years now. Good quality, maintained unit tests are more valuable to me than an IDE (and i honestly consider IDEs to be crutches).

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to Re: Auto-compile checking??? WTF? by jeffa
in thread Auto-compile checking??? WTF? by nysus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.