Re: [RFC_v3] Handling Backwards Compatibility in PEAR
| From: | Greg Beaver | Date: | Thu, 25 Sep 2003 01:42:51 +0000 |
| Subject: | Re: [RFC_v3] Handling Backwards Compatibility in PEAR | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-21956@lists.php.net to get a copy of this message | ||
Alan Knowles wrote:
[RFC3] Handling Backwards Compatibility in PEARNo problem. The reason I changed it is best exemplified by two existing PEAR packages: db_ldap db_ldap2 When db_ldap2's version 2.0 API comes out, it will be db_ldap22 under the old RFC, db_ldap2_v2 under the new one. I toyed with using just _2, but db_ldap2_2 is a bit confusing - is that ldap 2.2? I didn't post these arguments publicly, but it is good to make them clear. Regards, GregLooks good. The vX naming is rather ugly (from an aesthetic pov) but it does what it's intended to do.Butt Ugly - there doesnt seem to be any great advantage over the last proposal of Foo2 /Foo3... which I considered the best solution to a dirty problem.