So if you save incomplete syntactically wrong code more often than syntactically correct code, automatic syntax check on file save will be much more annoying than useful. (But wait, if you have to save completely broken code _so_ often, then maybe something _else_ is wrong here?)
It doesn't have to be "more often". Even if it's 1-in-10 times, it's still annoying. But, to make you happy, I do it the other way around. With a simple keyboard macro, I can syntax check the file I'm editing -- with as side-effect that the file gets saved*
Maybe root of your attitude to these things is lack of type-closing-brace-after-open-brace skill? ;-)
I've experimented with that in 1980s. Using some editor macros to automatically add closing parens, braces and brackets. I found that annoying, because when you're done with a block you now have to navigate over the already present brace.

Beside, if I now type a closing brace, my editor automatically de-indents (and it automatically indents when ending a line with an opening brace).

* 
 1 store-macro
   save-file
   shell-command &cat "/usr/bin/perl -c " $cfilname
~endm
bind-key execute-macro-1 ^A-c

[download]

In reply to Re^5: perlcritic speedup by JavaFan
in thread perlcritic speedup by powerman

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.