in reply to Re^2: Komodo 5.1 versus the others. (emacs)
in thread Komodo 5.1 versus the others.

Are you serious?

Thats far beyond what an IDE (or Komodo) can do, IDEs just integrate different (mostly external) development tools into one consistent environement.

Anyway if you know any AI program, which does this magical conversion, you can plug it in most editors I know.

In emacs you can select a textregion (e.g. a function), pipe it to an external program and replace the region with the output. All thsi triggered with one keystroke that you can define.

BTW: Thats the way I use perltidy ...

Cheers Rolf

UPDATE: Recommended read: Perl to C Converter? 8)

  • Comment on Re^3: Komodo 5.1 versus the others. (Perl to C)

Replies are listed 'Best First'.
Re^4: Komodo 5.1 versus the others. (emacs)
by Steve_BZ (Chaplain) on Sep 11, 2009 at 12:23 UTC

    Hi Rolf

    Nice article. The truth is of course that all languages have their uses. I took a long time choosing to use Perl, between Python, Perl and C++. I chose Perl, because I figured it had a shorter learning curve, higher productivity, a huge library of existing code (CPAN) and an active and centralised support community. I suspected Python might have higher productivity, but it didn't have a CPAN or a PerlMonks. I loved the idea of C++, enforcing rigour like an engineering discipline, I thought it probably had a lower productivity, and I just felt I didn't have the bandwidth to handle it. Finally, Perl seems to be more like a system glue. You can pretty much stick anything together with it. So, I'm a firm believer in Perl, I don't think it's going to disappear overnight, but there are some things I'd like to have in C++, maybe a spot of real-time video-frame processing, or a sensitive encryption algorithm, for instance. I'd prototype in Perl, because that's where I'm comfortable and then click the IDE button, switch between languages. Hey Presto and Voila!

    Regards

    Steve