Re: php5 packages - interfaces

Joe Stump wrote:

OK, the only questions I have now are ... 1.) Do we have an outlined upgrade path for package maintainers to follow for the php4 -> php5 transition?

err? not specifically but there are guidelines on how to deal with BC breaks (and making your package depend on PHP5 after previously working with PHP4 certainly is a BC break). Beyond that the QA team tries to help with making packages work both in PHP4 and PHP5 Anyways interfaces are nothing more than a "contract" and starting with PHP5 we now have a way to enforce these "contracts" with technical means. So to me interfaces or defining interfaces is not really a PHP5 thing. However I do think that there is benefit in using the PHP5 interface syntax to define interfaces for PEAR. These could then be used both for all packages in PEAR.

2.) Should I write up a PEPr proposal for a interface package? (maybe one outlining that other packages with factory methods should create their own as well? Kind of an RFC of sorts ...)

I am not sure if PEPr is the best place to start your efforts. I think that your best bet in getting something like this into PEAR is to collaborate with as many people on pear-dev as possible. Well this can probably be done with PEPr actually. All I am saying is that this task will take a lot of compromising. Actually this is more or less what people have been asking/opposing for a while: a regulation (guideline) on method names regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07