Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>> On my netbook (HP Mini 110) cperl-mode responds so slowly that it is
>> very annoying to type.
>
> Usually, cperl-mode is fast enough (most of my machines are about as
> powerful as a typical netbook).  So maybe you're just hitting a bug
> (tho, maybe you're hitting a pathological case, as well).
>
> Do you have some test case we can use to reproduce the problem?

If indeed this is a bug, I would call it a "showstopper" for cperl-mode.

Here is a recipe.  The file used below is the Oddmuse's Wiki engine.

mkdir ~/tmp

cd ~/tmp

wget http://git.savannah.gnu.org/cgit/oddmuse.git/plain/wiki.pl

emacs -Q

Here is a report from M-x view-lossage RET.  I do this:

1. C-x C-f ~/tmp/wiki.pl
2. M-x cperl-mode
3. C-s ApplyRules {
4. C-a
5. Move the cursor down a few lines
6. C-M-e.  Jump to end of defun. Move up a few lines to seek the comment
   line.
7. Type a few characters

(5) is slow. (7) is very slow.  Meaning it takes ages for the 10 or so
characters to be echoed.

Interestingly, after (2) I see the following message reported by
cperl-mode.  I am not sure whether the error is a cause for slow
performance.

Anyways, if I do,

    perl wiki.pl

I don't see the perl complaining about the file being bad.  So there is
a bug somewhere.

Apart from the recipe above, you can try the following

1. Mark the ApplyRules sub.
2. M-x indent-region it.

With perl-mode, (1) and (2) is very quick.  But with cperl-mode things
are bad.



--8<---------------cut here---------------start------------->8---
End of `qw( ... )' string/RE not found: (scan-error Unbalanced parentheses 1543 155427)
--8<---------------cut here---------------end--------------->8---

--8<---------------cut here---------------start------------->8---