On Sat, Jan 18, 2014 at 8:39 AM, Peter Corlett <ab...@cabal.org.uk> wrote: > On Fri, Jan 17, 2014 at 10:18:14AM -0000, Andrew wrote: >> Looking to try using an Integrated Development Environment. > > Why? What problem are you having that you expect an IDE to solve?
He wants to *try* it. > The features I find most compelling in IDEs is background parsing to > immediately spot syntax errors and be able to auto-complete or otherwise spot > typoes or confusion about what type a method returns. However, this only > really > works with statically-typed compiled languages such as Java. Perl is very much > the antithesis of Java and you don't really get these benefits. Yes you do. It's 2014; parsing dynamic languages in IDEs is largely solved. Any difficulty in finding such a thing for Perl is more a reflection of Perl's status as a language in 2014 than any intrinsic technical difficulty. > They also provide various hot keys and shortcuts to perform test compiles, VCS > integration and whatnot, but that's really only of marginal benefit. Says you. Maybe the OP would like to *try* it and not have someone second guess their own motivations & preferences? Maybe they've read something like http://www.jetbrains.com/ruby/features/ and thought wouldn't they like that for perl? These "oh but emacs/vi/nano is great!" responses are really irrelevant. Paul