On Mit, 17 Okt 2001, Michael Bedy wrote:

>   It looks to me like QRegEx gets very close, but misses a few crucial
> features. The biggest of these is lack of /m support and all the various
> things that go along with it. Also, the "." atom always matches newlines
> in QRegEx. This is equivelant to the /s option in Perl, but Javascript
> unfortunatly requires that "." not match newlines.
> 
>   In addition, the /g option is not directly supported in QRegEx, however
> it could be emulated with a little bit of work.

As far as I know we don't support /g currently at all :-( (which breaks 
google directory btw, so it needs urgent fixing!). 

do you think it would be possible without many hacks to add an translation 
layer between javascript regexp and QRegexp? Although pcre is small, 
dropping an additional dependency is nice. 

>   I'll probably work on this this weekend. I've kinda been out of the KDE
> loop until a week ago. When are the feature freezes and stuff?

No problem, this is bugfixing ;)


Dirk