On Mon, 2009-11-09 at 15:49 +0000, David Otton wrote:

> 2009/11/9 Tony Marston <t...@marston-home.demon.co.uk>:
> > Because I can't do that until I install PHP 6, but as I never play with beta
> > software waiting for it to go live will be too late.
> Not sure why not. If it's just the name collision, call them
> alt_ereg*() until ereg*() goes away. In fact, it's much easier to
> write unit tests against your new functions if the old functions are
> still hanging around.
> > I've tried looking at the PHP wiki, but I cannot see any method of
> > creating an RFC.
> Well, the RFCs are here, but you probably already found them:
> http://wiki.php.net/rfc (register is in the bottom-right corner).
> Can't help you with your php-internals problem, I'm afraid. Tried
> emailing the list manager?
> > I have, however, created a request in php_compat in the PEAR system at
> > http://pear.php.net/bugs/bug.php?id=16769
> Fair enough. Good luck.

And what about something like this as an internal wrapper:

    function ereg_*()


And you should at least try to test the code you write for your clients
on PHP6 if that is where it is going to be hosted before servers are
upgraded, even if it's just to find out if it will break and give you
time to fix it. Hell, you could probably charge for that if the client
absolutely has to be on a PHP6 server, as something like that would fall
outside the scope of future maintenance, unless of course you wrote your
code in full knowledge of the change that would happen in PHP6.


Reply via email to