[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#30681: It starts to come back now...
From:       David Faure <david () mandrakesoft ! com>
Date:       2001-10-15 12:18:26
[Download RAW message or body]

On Lundi 15 Octobre 2001 11:55, Michael Bedy wrote:
>   Hi,
> 
>   I'm starting to remeber the issues now...
> 
>   The more I think about it, the more I think making it manditory is a
> good idea. Or, perhaps, shut off regex support completely if you don't
> have it.
> 
>   The reason is that the POSIX regex used as the fall back is not a subset
> of the Perl regex used by js, but instead a completely different syntax.
> Even simple regular expressions designed for js are likely to not work
> with POSIX. Simple things like character classes are completely different.
> (i.e., I recall that [0-9] is not legal in POSIX. It's [:numeric:] or
> something like that.) Worse yet, regex written for the js syntax may be
> legal POSIX syntax, but mean something completely different.

Ouch!

>   But, to be honest, I really don't care either way. I give you the above
> information so that those who do care can take it into accout :-)

I just discussed this with Harri, and we reached this conclusion:
it makes sense to require libpcre only when the regexp support is actually
complete. The current support isn't complete, and not only due to the multiline
option, but also to features like $1 etc. I suggest to complete the regexp 
support, and then make libpcre mandatory.

Thanks !

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://perso.mandrakesoft.com/~david/ , http://www.konqueror.org/
KDE 3.0: Konquering the Desktops

[prev in list] [next in list] [prev in thread] [next in thread]