On Tue, 13 Aug 2002, Dan Kalowsky wrote:
> On Tue, 13 Aug 2002, Marcus [iso-8859-1] B�rger wrote:
>
> > The point is to be able to direct to external sites not on php.net! For
> > example
> > when a function is just a wrapper around a library then you can use the
> > absolute
> > form of the docref parameter ("http://<site>") to point to the library's
> > website.
>
> Okay thats a point I hadn't thought of. Though I'm not sure why we'd be
> referencing outside sites. Can we then change the CODING_STANDARD
> example to NOT use the php.net website? Hopefully stopping anyone from
> using it as a reference to any php-specific documentation, and only for
> external sites.
Do you think this will help the lost PHP script writer? For example, the
cURL extension is really just a wrapper around libcurl. If they get an
error on curl_setopt() do you really want to direct them to the C API
docs on the cURL site? I think it should always point to the php.net
manual; external sites won't help the PHP script writer with their PHP
code. From the PHP manual they can go to library website if need be.
My $.02.
--Ricky
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
