Re: XML_Tree - Lets Fix this up finally

From: Date: Sun, 20 Feb 2005 03:50:19 +0000
Subject: Re: XML_Tree - Lets Fix this up finally
References: 1 2 3 4 5 6 7 8 9 10 11 12 13  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-2479@lists.php.net to get a copy of this message
On Sat, 2005-02-19 at 14:05 +0100, Lukas Smith wrote: > Alan Knowles wrote: > > > - Guareentees code compatibility, if your code worked with 1.* then it > > will always work with 1.* > > So are you suggesting a pragmatic approach here? As in the developer may > break BC by mistake and if he feels that some changes bear the danger of > a BC break but he does not intend to break BC he should upgrade the > major version number but not create a new package? > > Or are you saying that upgrading the major version number but not > creating a new package is for changes that change the internal structure > and will therefore break BC for package that extend the package (rather > than using its public API)? I think it's going to be impossible to make a hard and fast rule on this. - I guess the preference is that if you think it may break users code in anyway, and there are no simple workarounds / to solve the problem, then release it as a new major version. the clone/cloneNode in XML_Tree is a bit of an oddity.. the clone function in it will break totally in PHP5 - so releasing a new package that breaks BC is probably doing people more good than harm.. (especially if the clone() method is commented out or something - so they have a workaround, but are aware of the issue..) Regards Alan > > regards, > Lukas > -- Alan Knowles <alan@akbkhome.com>

« previous php.pear.qa (#2479) next »