Re: Basic install problem
| From: | Geranium | Date: | Mon, 26 Aug 2002 16:26:41 +0000 |
| Subject: | Re: Basic install problem | ||
| References: | 1 2 3 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-2195@lists.php.net to get a copy of this message | ||
Thanks for the help, Pierre-Alain.
I tweaked my include path, and pear's now working, but I'm left wih the
impression that the documentation could use some work!
Unless there's some neat trick to using pear without include/require
commands, most of the docs examples won't work. For example, I wanted
to try out the Mail_RFC822 class. If I just copy the examples from the
docs here:
http://pear.php.net/manual/en/core.mail.rfc822.php
They won't work because they can't find the Mail classes. So I added:
require("Mail.php");
But that doesn't help, even though Mail_RFC822 is a part of the mail
package. So after some rummaging through the code in Mail.php, I found
references to the RFC822 class, so I amended my require to:
require("Mail/RFC822.php");
and I'm glad to report that it now works. This doesn't seem to be
documented anywhere, even though it's completely fundamental to having
pretty much anything in pear actually work. Does this pattern apply to
the whole of pear?
Can I request that any examples include the necessary include commands
to make them work without such tweaking? Also, how can I contribute to
documentation?