Something like Komodo is an excellent way to debug code, much in the same style as the Visual Studio debugger.

For me, the problem with Komodo was its rather feeble code editor. I prefer Vim (though I have nothing against Emacs).

I'd like to think that the development of Perl 6 could be a rallying call for perl tool developers. The Reinvigoration of perl (in a commercial, enterprisey, hype-y sense) that is sure to follow Perl 6's release should not be dragged down by pathetic development tools.

Visual Studio and Eclipse are both excellent environments feature-wise (ignoring VS bugs and Java idiosyncrasies); it'd be sad not to have available tools of that callibre - for Parrot's family of languages - after the release of Perl 6.

Key features I'd want:

• Debugging: Edit and Continue support (ala VS debugger)
• Pluggable code-editor (eg: VS + ViEmu)
• Webservice discovery, client side code generation
• Packaging templates for various deployment types
• High-quality templates for CPAN module development
• Well integrated support for many forms of testing.
• Automatically set computer alight if UML diagrams even smell like being used

-David

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.