Hi Edi,
thanks for your response.
Edi Weitz edi@agharta.de wrote: [...]
Now, using another kind of structures (like, say, your buffers) that aren't strings but are random-access - that wouldn't be /too/ hard. It would involve going through three or four files and change SCHAR to something else but basically I don't really see a problem. However, as CL-PPCRE has a reputation for being quite fast I wouldn't want to sacrifice this for greater flexibility (buffers instead of strings, arbitrary objects instead of characters - you name it). I think the right way to do it would be to offer the ability to build different versions of CL-PPCRE based on *FEATURES*, i.e. at compile time you decide whether you want a fast regex engine for strings or if you want a not-so-fast regex engine for, say, buffers. Would that be OK for you?
That sounds good from this end. I'll look at this over the weekend, since hopefully it shouldn't be too much effort. If the patches aren't too invasive, would you want them? Otherwise, we'll just try and keep a version of cl-ppcre in climacs, and update it as and when.
Thanks again,
Lawrence