Why would Komodo be messed up though?

See Re^7: threads->new falling in a heap. for a few hints. Then go and ask the Komodo people for support.

The difference is in (?-xism: vs (?^: which is what I get.

The sequence (?^: isn't a legal perl regex construct, so any module that was producing that sequence would never work anywhere.

It is really hard see how a well-known and used module like Regexp::Assemble could produce such an error?

What editor do you use or recommend?

I've been using TextPad for about 15 years. It is far from perfect, but it rarely lets me down...

For all I know Komodo may be a brilliant editor, but as I said in the link above, I wouldn't want to base my earning of a crust upon such a complex piece of software. Not only are you subjecting yourself to the risks of the Komodo programmer's work; but also those of the programmers of half a dozen different language runtimes and the interactions between them.

And any editor that requires 11 kernel threads to edit a single file; in addition to the 32 kernel threads is uses just to start up, is just asking for trouble. It is essentially a lottery machine that is bound to screw up randomly.

I'm a strong advocate of threading, but 43 threads, 6 run-times and goodness knows what other technologies all in a single process? There is simply no way to reason about all the possible states that can exist; much less test them all. It is simply numerically impossible.

At the very least, stop running your perl code from within the editor. Run it from the command line. If it screws up then, you at least know the editor isn't the source of the problem.