On Sat, 10 Aug 2002, Marcus Börger wrote:
> +This can be done automaticall with the use of php_error_docref. Where the
> +docref parameter is either NULL or a manual reference describing the
> +error in detail. This must be an external url started by "http://"; or
> +the name of a
At 01:04 10.08.2002, you wrote:
>In-Reply-To: <[EMAIL PROTECTED]>
>Message-ID: <[EMAIL PROTECTED]>
>MIME-Version: 1.0
>Content-Type: TEXT/PLAIN; charset=iso-8859-1
>Content-Transfer-Encoding: 8BIT
>
>On Sat, 10 Aug 2002, Marcus Börger wrote:
>
> > +This can be done automaticall with the use of
Proposal for CODING_STANDARDS
cvs -z3 -q diff CODING_STANDARDS main\main.c (in directory S:\php4\)
Index: CODING_STANDARDS
===
RCS file: /repository/php4/CODING_STANDARDS,v
retrieving revision 1.14
diff -u -r1.14 CODING_STANDARDS
---
O.k. here it comes:
First thanks to Wez for another great idea.
The order of parameters and the function names have changed. The
order is now docref TSRM, optional parameters and starting from type
the original parameters of php_error. This order makes it easier to change
php_error calls into ph
