Re: PEAR Status
| From: | Jon Parise | Date: | Sat, 24 Jun 2000 19:20:46 +0000 |
| Subject: | Re: PEAR Status | ||
| References: | 1 2 3 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-119@lists.php.net to get a copy of this message | ||
On Sat, Jun 24, 2000 at 08:37:41PM +0200, Ulf Wendel wrote:
> I would like to develop some kind of standards for each of these topics
> before making PEAR "public":
>
> - inline documentation
We decided to go with the "official" javadoc documentation conventions
for the Horde packages:
http://java.sun.com/products/jdk/javadoc/writingdoccomments/index.html
> - documentation (API, cookbook, reference, integration into php.net)
This would cover conversion to XML so it could be dumped into the jade
rendering chain, then?
> - error handling
Yeah, this is a big one. At this point, it seems that each package
just defines its own return values (FOO_OK = 1, FOO_ERROR = -1, ...).
This is only discussed tangentially in the current http://pear.php.net/
(suggested) guidelines.
> - how to I define what belongs to a package
As in some sort of manifest?
> - installation of packages
> - configuration of packages
These are biggies, too. Is the goal to move toward something like
CPAN?
--
Jon Parise (jon@csh.rit.edu) . Rochester Inst. of Technology
http://www.csh.rit.edu/~jon/ : Computer Science House
Member