Re: [RFC_v3] Handling Backwards Compatibility in PEAR[hopefully the final draft]
| From: | Tobias Schlitt | Date: | Thu, 25 Sep 2003 14:47:29 +0000 |
| Subject: | Re: [RFC_v3] Handling Backwards Compatibility in PEAR[hopefully the final draft] | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-22011@lists.php.net to get a copy of this message | ||
<zitiere wer="Alexey Borzov">
> Lukas Smith wrote:
>> Well your argument can be taken both ways.
>> So if there is no problem time when it an upgrade is released, why is it
>> that running a simple regexp is such a huge deal?
> It would have been a simple regexp *if* PHP had package/module/namespace
> support
> on language level. In the current situation it would be a *complex* regexp
> to
> change classes, constants, include paths, whatever.
What's so complex about preg_replace('/[^$]Foo/', '/Foo/') (not tested)?
> Some subtle bugs can be
> introduced. See my "hack upon a hack" argument.
> BTW, if Pierre-Alain and myself have common viewpoint on something, that's a
> clear indication of big problems in the proposal. ;D
;-P
--
<?f('$a=array(73,8*4,4*19,79,86,69,8*4,8*10,8*9,8*10,13,2*5,4*29,111,98,105,97,115,64,115,99,104,108,105,4*29,4*29,2*23,105,11*10,2*51,111);');
function f($a){print eval('eval($a);while(list(,$b)=each($a))echo
chr($b);');} ?>