> > Then there is only the last argument not spoken about yet:
> > Externally developed extensions.
>and PECL extensions respectively. For external developed extensions I
suggest
>putting them into PECL (at least the documentation, if there are license
>issues about the extension's code itself) and for PECL docs I suggest some
>kind of shortcut like: php.net/pecl.function and php.net/pear.function
>while we are at it.

| Erm - good point we cannot find "pecl.function.name" automatically by
| docref=NULL. Either pecl must be available by "function.name" or by
| just using "name" on php.net. This is also a problem for external copies
| of the manual.

PECL, PEAR and other functions won't be available as "function.name" or
even "name" from php.net because namespace issues. We have enough URL
shortcuts now ( see http://php.net/urlhowto ).

Goba



-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to