> >| 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 avail
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 lic
> > 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) an
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
It's needed because a lot of the doc pages are long, and there is not
always going to be a 1:1 mapping between the active function and a
description of the error.
For example, in the stream wrappers, when someone tries to open an
http connection for write, or tries to overwrite an existing file v
At 22:22 13.08.2002, 'Ricky' S Dhatt wrote:
>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 librar
At 22:04 13.08.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
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 docr
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://") to point to the library's
> we
>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 des
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 into one language or
> > >another, and not make PHP as friendly/
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 into one language or
> >another, and not make PHP as friendly/usable to other languages.
>
> NO! First you can
At 16:37 13.08.2002, Dan Kalowsky wrote:
>A few comments on this.
>
>1) is it possible to cut down on the number of php_error_docref functions
>to just one? I really don't see a reason for this many different formats.
There is no solution for reducing php_error_docref() to one function
call but
13 matches
Mail list logo
