Re: PCRE/Extended-POSIX portability in PEAR packages

Daniel Convissor wrote:

Hey Philippe: On Sun, Aug 22, 2004 at 02:38:12PM -0400, Philippe Jausions wrote:

So your solution, is "no" solution ;-)

I don't really see it as a problem to begin with. pcre is a vital part of any programming language. Administrators who turn it off on their systems are significantly limiting the system's functionality for themselves and their users. I've never ran into a system that had it disabled. Over the few years of being involved with PEAR, this is the first time I recall a discussion on this matter.

Me too, I was surprised to see such a limited installation of PHP... However, it's there. Even if rare, ignoring it is the same as saying: "my application works only with MySQL because that's what my system has" With PEAR::DB, MDB, ADO and so on available, you wouldn't think it's a clever way to code. Let's not confuse PCRE and regular expressions... I would say RegEx are vital part, not PCRE (although I like PCRE better over extended POSIX.) All I'm saying is, if a package can work with both PCRE and extended POSIX functions, why not make it work with both at a minimum extra cost? Note that it's not a matter of backward compatibility issue, but portability. -Philippe