Ilya Zakharevich is working on a new release of cperl-mode and would like testers. See http://groups.google.com/groups?threadm=dj1k2s$1kq9$1@agate.berkeley.edu.

(Note that he has gone through several revisions since his first message; I think the version number is up to 5.10 now.)

  • Comment on new version of emacs cperl-mode available for testing

Replies are listed 'Best First'.
Re: new version of emacs cperl-mode available for testing
by monarch (Priest) on Oct 25, 2005 at 03:29 UTC

    I love cperl-mode! When byte-compiling I got:

    My emacs-version's value is "21.4.1". Using cperl-mode.el.5.10. On Linux version 2.6.12-1.1390_FC4 (bhcompile@decompose.build.redhat.com) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #1 Tue Jul 5 19:58:55 EDT 2005

    Update: it certainly seems much quicker in parsing a buffer!

      If you haven't already, please report this to Ilya, either directly (yes, the nospam-abuse is really in his address) or in the clp.moderated thread or both.
      Aarrgghh!

      It seems between cperl-mode v5.0 and v5.3 something broke. I have a file with perl code that sends my emacs into a tight CPU spin and the only way out is to kill emacs-x!

      update: it appears that having space characters on empty lines following a piece of code takes an exponentially long time to process (depending on how many space characters there are).. The following code exhibits this problem:

      #.-*-CPerl-*- { ....foreach.(.qw(.hello.goodbye.).).{ ........if ( 1 ) { ............my ...... ............
      but be sure to s/./ /sg before loading this into cperl-mode! You'll note that every space character you add to the 2nd last line will take an exponentially longer time to process.

      update: after e-mailing Ilya Zakharevich yesterday I've already had a response, and v5.14 of cperl-mode has been released which handles the scenario I wrote about here! Great stuff!