Catching typos and integrating documentation ... now those are useful things, so long as they are requests and not requirements. I personally despise the hard-integration that some IDEs have that says "I will offer my suggestions NO MATTER WHAT YOU WANT cause I think you're a bloody idiot." At that point, give me Notepad or you'll have a piece of paper that says "I quit!" shoved up your nose.

Now, Ovid and I have each separately created vim macros for working with test suites and doing syntax checks on a file. Sure, I can see the benefit of those things. I even have skeletons for when I create a new file that generates those lines you're talking about and it's different for a .t vs. a .pm/.pl. Though, frankly, I should be using something like Test::Class or some other xUnit framework so that my setup and teardown can be DRY'ed.

But, what does it tell you that you need a program to manage your project?

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re^7: Steve Yegge on how to build IDEs and improve speed of dynamic languages by dragonchild
in thread Steve Yegge on how to build IDEs and improve speed of dynamic languages by zby

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.