From: moshez at math.huji.ac.il (Moshe Zadka)
Date: Mon, 26 Apr 1999 01:36:05 +0300
Subject: Python too slow for real world
In-Reply-To: <y0j7lr0obcs.fsf@vier.idi.ntnu.no>
References: <372068E6.16A4A90@icrf.icnet.uk> <3720A21B.9C62DDB9@icrf.icnet.uk> <3720C4DB.7FCF2AE@appliedbiometrics.com> <3720C6EE.33CA6494@appliedbiometrics.com> <y0jaevznhha.fsf@vier.idi.ntnu.no> <glmvhemn4zx.fsf@caffeine.mitre.org> <y0j7lr0obcs.fsf@vier.idi.ntnu.no>
Message-ID: <Pine.SUN.3.95-heb-2.07.990426013235.1500B-100000@sunset.ma.huji.ac.il>
Content-Length: 1103
X-UID: 755                                                  

On 25 Apr 1999, Magnus L. Hetland wrote:

> > Um, why?  I don't see any need at all for them to move from
> > module-status to core-language-status.
> [...]
> > 
> > In all seriousness, what reason do you have for making that
> > suggestion?  I am willing to believe that there might be a good reason 
> > to do so, but it certainly isn't immediately obvious.
> 
> Now, that's really simple -- because re.py is slow. I thought maybe
> some of the slowness might be improved by a c-implementation, that's
> all. Not too important to me...

Um....two wrong assumptions here:
1. C implementation is /not/ the same as core status: C extension modules
are numerous and wonderful, for example...
2. re.py is a (very thin) wrapper around pcre, a C extension module for
Perl Compatible Regular Expressions.

Which just goes to say that while pcre can certainly be optimized, it
can't be done by simply rewriting it in C.
<0.5 wink>

but-we-can-always-call-Perl-on-the-fly-to-evaluate-regular-expression-ly
y'rs,
Z.
--
Moshe Zadka <mzadka at geocities.com>. 
QOTD: What fun to me! I'm not signing permanent.





