I've used Komodo IDE for many years. It's editor engine is the same engine used for Sublime Text so there is a lot of feature cross over in the editors. When I'm developing Perl code I pretty much never leave Komodo. It's debugger support is great and the IDE integrates well with test and coverage tools. Common revision control systems are well supported. And these days it is essentially free, although if you are doing a lot of script coding it was worth the price of admission even when it was a pay for product.

An editor war? Why not? ;) Seriously though, Notepad++ is great, or Vim has Windows builds.

I feel confident it wouldn't be the first editor war and most certainly won't be the last in the Monastery :P

While we are making editor suggestions, I find GNU Emacs and its cperl-mode to be very useful for writing Perl code.

What grandfather meant with "background syntax checking" is called flymake-mode in emacs.

It runs regularly perl -c in the background and highlights problematic lines. And strict will cause compile-time errors, like with undeclared variables.

I know that Komodo offers it too. Not sure about vim or notepad++ or alike.

Though I don't share his confidence that code which evolved without strict can be easily fixed with these tools. I rather share Bill's analysis.

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery}

Though I don't share his confidence that code which evolved without strict can be easily fixed with these tools

Um, I don't think I expressed that confidence. I did say:

With modern editors that perform background syntax checking it's pretty quick to identify where variables need to be declared and fix that.

which as BillKSmith points out may be the thin edge of the wedge, as indeed you also imply. However, identifying issues is a huge head start in resolving them!

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond

Quibble: flycheck >>> flymake. It comes more or less out of the box with both perl -c and Perl::Critic support.

The cake is a lie.
The cake is a lie.
The cake is a lie.

The syntax highlighting in Emacs' cperl-mode is extensive and tends to catch most of my syntax errors when I notice that the code did not highlight as expected.

This is particularly useful for catching sigil and subscript typos — CPerl mode highlights direct array and hash lookups accordingly, so if I miss the shift key and type $foo[bar] instead of $foo{bar}, the syntax highlighting will indicate my mistake almost instantly.

I know that Komodo offers it too

I have downloaded and installed Komodo and it certainly looks impressive. I think I need quite a while to find my way around and start using it to produce something but I shall certainly give it a good try...

I did think of Padre but that doesn't seem to be being developed or supported anymore.

"should I be looking at anything else?"

I use intelliJ IDEA as my IDE, with the Camelcade Perl5 plugin, and Devel::Camelcadedb distribution which allows in-IDE debugging. Of course, I also have the Vim plugin installed in the IDE as well. Been using this setup for years. I've got their Open Source license, but the free version works all the same.

Here's an image I saved quite some time ago.

That looks rather like Eclipse which I used briefly at university when I had to produce some Java code. The little bit of Java I use now is for Android app development and is done in Android Studio.

I'm guessing it is rather more powerful than Text Pad which I currently use. This does provide Perl syntax highlighting but not much else.