Re: Re: File_SearchReplace API and versioning

From: Date: Sun, 04 Dec 2005 15:30:25 +0000
Subject: Re: Re: File_SearchReplace API and versioning
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-40586@lists.php.net to get a copy of this message
Hello Lukas, From Sunday, March 13, 2005, 10:01:14 PM, you wrote: >> The only problem with API is that now replacement is done by default. >> After modification it will be done explicitly. It is sure a BC break, >> but how to estimate the impact? LS> The impact is that you need to create a new major version, which LS> effectively means creating a new package called File_SearchReplace2. LS> However it sounds more like you should handle this through options, LS> optional parameters or an additional method than with a new package. I can't handle this through options, because I need to change default behavior to make the use of package easy and safe. This is explained here: http://pear.php.net/pepr/pepr-comments-show.php?id=281 It seems to me, that I've found the solution. http://pear.php.net/group/docs/20040226-vn.php I will release latest 1.1.0 version without Search capability and then will make 2.0.0 release. Is it ok? t --

« previous php.pear.dev (#40586) next »