Hello, this is Shane from ActiveState, lead for Komodo. While I agree that it looks like we don't do much for Perl in Komodo at this point, it's largely due to the fact that it (and Python) were the first languages that we supported deeply feature-wise.
In Komodo 4, the primary work around Perl was the rewrite of the code parser for autocompletion/code intelligence and improvements in the debugger. Komodo 4 was and is focused on improving usability for web development. From that aspect, we focused largely on area's we did not have good support already, such as RAILS, JavaScript, HTML, CSS. We also implemented "multi-language" editing to make adding support for stuff like Template Toolkit possible.
So while there are not major new features specific to Perl in K4, if you're using Perl on the web, there are lots of useful improvements for you.
For Perl 6, well there isn't really an approaching 1.0 release of it at this time and only bleeding edge pickup on it. If someone wanted to add Perl 6 syntax support to Komodo, it can be done via UDL (our own language definition syntax). Once things progress further with Perl 6 we ***WILL*** be adding support.
BTW, upgrades from 3.5 are much less than the list price, see our store for details.
Regards,
Shane
-
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.
|