Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Day 1473: PPI now line-noise compatible and going into pugs! More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

EPIC Developers say PPI is too slow for an editor (Score:1)

by clscott (4354) on 2005.12.15 12:59 (#45188) Journal

EPIC Developers say PPI is too slow for an editor to use.

http://sourceforge.net/forum/forum.php?thread_id=1386755&forum_id=258687 [sourceforge.net]

Reply to This
- Re:EPIC Developers say PPI is too slow for an edit (Score:1)
  
  by Alias (5735)
  
  Nope, he says it's too slow to do syntax highlighting in real-time with.
  
  And he'd be right. I've said that from the start, although there are some potential techniques for windowing that might help.
  
  PPI would be used in background mode. Parsing and analyzing in a background process and feeding event and feedback objects back into the editor.
  
  The speed problem won't go away until PPI gets 4 times faster than it is now. But the "can accept any old shit" problem is solved now.
  
  Which means we are go for background

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.