Hi,
On Tue, Aug 13, 2002 at 05:26:17PM +0200, Marcus Börger wrote:
At 17:05 13.08.2002, Dan Kalowsky wrote:
On Tue, 13 Aug 2002, Marcus [iso-8859-1] Börger wrote:
2) Can we please remove the http://www.php.net/manual/en/blahblahblah;
style of use for this? It will tend to force users
At 10:03 14.08.2002, Jan Lehnardt wrote:
Hi,
On Tue, Aug 13, 2002 at 05:26:17PM +0200, Marcus Börger wrote:
At 17:05 13.08.2002, Dan Kalowsky wrote:
On Tue, 13 Aug 2002, Marcus [iso-8859-1] Börger wrote:
2) Can we please remove the
http://www.php.net/manual/en/blahblahblah;
style
Hi,
On Wed, Aug 14, 2002 at 10:09:52AM +0200, Marcus Börger wrote:
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
At 10:15 14.08.2002, Jan Lehnardt wrote:
Hi,
On Wed, Aug 14, 2002 at 10:09:52AM +0200, Marcus Börger wrote:
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
Hi,
On Wed, Aug 14, 2002 at 10:25:40AM +0200, Marcus Börger wrote:
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.
erm,
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
At 10:57 14.08.2002, Gabor Hojtsy wrote:
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
| 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
So, you're suggesting that all external extensions have to be in PECL
in order for the error message to link to further documentation??
What about projects like APC/APD? SRM?
NameOfYourFavouriteThirdPartyBinarySCEHere?
Do they all have to be hosted on php.net??
--Wez.
On 08/14/02, Jan
Hi,
On Wed, Aug 14, 2002 at 10:41:24AM +0100, Wez Furlong wrote:
So, you're suggesting that all external extensions have to be in PECL
in order for the error message to link to further documentation??
What about projects like APC/APD? SRM?
NameOfYourFavouriteThirdPartyBinarySCEHere?
Do
php_error_docref(function.fopen TSRMLS_CC, E_WARNING, Spongebob Square
Pants lives in a pineapple under the sea);
To me that should be the recommended method, as it will allow the php.ini
values for language to override everything nicely, and everyone can see
the PHP manual in their desired
11 matches
Mail list logo
