Re: [PEPr] +1 for File Formats::File_XSPF
| From: | Joshua Eichorn | Date: | Thu, 08 Dec 2005 19:14:57 +0000 |
| Subject: | Re: [PEPr] +1 for File Formats::File_XSPF | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-40670@lists.php.net to get a copy of this message | ||
Hannes Magnusson wrote:
On 12/8/05, Pierre <pierre.dev@gmail.com> wrote:You do not like, fine, but it is not acceptable. You do not have the choice to play with the names. Using php5 only justifies a new major version, unless all you want is to replace var (which will be soon a non problem) and do not use any new features. Keeping in mind that this solution is only for the transition, the "natural" evolution will help here, in 1-2 years, the majority of the new packages will be php5 only. --Pierre In 1-2 years we should be working on PHP6 packages. Being 3years, and a whole major version, behind is in no way acceptable. The internet as we now it could be dead by then. The US presitend could be a woman. Things change, rules do too. Its not more then 10years since it was _legal_ to kill an Turkish men in Vestmanneyjum, Iceland... We need to follow the evolution. We can't keep punishing people who do. If we were talking about whole lot of new features then its OK to increase/insert the version number of the package. Im not talking about that. Just creating PHP5 OO version of the package. As I said, having PHP5 and PHP4 versions of the exact same package. Nothing more. Nothing less. When/if new major features are introduced, fine, bump in a digit in the name indicating a major changes. Once the 'var' keyword gets aliased to 'public' I'll think about stfu though ;) but E_STRICT doesnt make the package PHP5 based... You can't have incompatible code with the same class name period, end of discussion. If i use a package in php4 and then upgrade to php5 and run pear upgrade everything shouldn't break. Now maybe we can talk about something where you use a factory to get the class and you can specify the php4 or 5 api, but i think thats more of a hack the class2. -joshOn Thu, 8 Dec 2005 19:00:20 +0100 hannes.magnusson@gmail.com (Hannes Magnusson) wrote:This is not acceptable at all. FooBar2 means "take two, second major release" in my minds (Net_FTP & Net_FTP2 for instance). There currently is *no* way to have both PHP5 and PHP4 package for the exact same purpose without playing games with names.On 12/8/05, Lukas Smith <lsmith@php.net> wrote:FooBar - php4 FooBar2 - php5David Grant wrote:Could you be a little clearer? How would I go about achieving this?