AW: [PEAR-DEV] Meeting: Topic Proposal
| From: | Daniel Khan | Date: | Tue, 01 Apr 2003 10:47:29 +0000 |
| Subject: | AW: [PEAR-DEV] Meeting: Topic Proposal | ||
| References: | 1 | Groups: | php.pear.dev php.pear.doc |
| Request: | Send a blank email to pear-dev+get-14748@lists.php.net to get a copy of this message | ||
Richard Heyes wrote:
[..]
> For the record, and particularly since I won't be around at the
> time of the
> meeting, after discussing this in IRC myself and Christian Dickmann
> are a firm -1 on new packages having to have documentation.
I know I'm pretty new here and I may not know anything about discussions
in the past - but what are the reasons for that?
I am thinking about CPAN. It has a very clean and short docu for each module
and I really needed this doku when I programmed perl.
Also in PEAR I never was smart enough to figure out how a package works
without having any doku.
Sometimes good tutorials can be found with google - but having that in PEAR
would be very nice.
Just one example (no offense to anybody):
There is a package in PEAR. It was only useful for me if it had one
particular feature.
I finally found a short example which basically implemented what I wanted to
do.
Looking at the method inside the source code to figure out how it exactly
works I found the following description:
/**
* Black magic :)
*/
Hm - as I'm doing white magic most of the time I decided to better not use
the package :))
Just my 2 cents
--
Daniel [datenPUNK] Khan