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

PurePerl speed 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.

It may be obvious, but... (Score:1)

by godoy (2167)

Matt, it may be obvious, but have you compared the algorithms used at xmllint and your Pure Perl parser?

C allows some optimizations where Perl allow them to occur in other places.

--
-- Godoy.
- Re:It may be obvious, but... (Score:3, Interesting)
  
  by Matts (1087)
  
  The problem is that Perl is just slow. Not really much I can do about that. When you compare it to C, where it can do really nice things like char = ++*p to get the current character and move to the next byte in a string . With perl a similar idiom is: $char = substr($str, 0, 1, ''), which has a lot more overhead (same for a regexp to do the same). Character-wise coding in perl has always been a bit of a pain.
  - Re:It may be obvious, but... (Score:2)
    
    by Matts (1087) on 2002.02.04 7:02 (#4037) Journal
    
    Err, that should have been char = *p++.
    
    My C sucks ;-)
    
    Reply to This
    
    Parent

Get More Comments

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