[PEPr] Comment on XMPP::JAXL

From: Date: Mon, 27 Dec 2010 11:08:43 +0000
Subject: [PEPr] Comment on XMPP::JAXL
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-53915@lists.php.net to get a copy of this message
Hi, I have made a few changes to the library as required by PEAR coding standard but my biggest fear still remains with Jaxl library file and class naming convention. The folder structure looks like: - /core -- jaxl.class.php -- jaxl.something.php - /xmpp -- xmpp.class.php -- xmpp.get.php -- xmpp.something.php - /xep -- jaxl.0045.php -- jaxl.0060.php - /env -- jaxl.ini -- jaxl.js Applications should simply do: require_once '/path/to/jaxl/core/jaxl.class.php'; Jaxl class have an internal class loader method which automatically includes other library folder files into the environment. The class names are like: JAXL, JAXLUtil, XMPP, XMPPGet, JAXL0045, JAXL0060 etc which is again something not as per pear coding standard. Changing file names and internal class names will be a big big change for library and it's existing users. Is there a workaround so that file names and class names can remains as it is, and Jaxl library can be submitted to pear repository. Ofcourse, other pear coding standards will be followed as defined. -- http://pear.php.net/pepr/pepr-proposal-show.php?id=635

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