Joining the phpdoc team. General manual maintenance; fixing errors, adding new
documentation, updating old documentation, etc. Might join the Japanese translation
team as well (undecided).
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.ph
It's actually quite beneficial to leave it off in included files.
Trailing carriage returns will not mess things up for any headers that
might be sent after the include if you leave off the closing ?>
-Rasmus
On Sat, 15 Nov 2003, Jon Parise wrote:
> On Sat, Nov 15, 2003 at 07:14:54PM -0500, R
At 07:14 PM 11/15/2003 -0500, Robert Cummings wrote:
Hi all,
Could someone let me know if omission of the closing php tag from a
source file without generating an error is a bug or a feature? I've
always thought it a feature, but someone suggested on the general list
that it's a bug.
It's a featur
On Sat, Nov 15, 2003 at 07:14:54PM -0500, Robert Cummings wrote:
> Could someone let me know if omission of the closing php tag from a
> source file without generating an error is a bug or a feature? I've
> always thought it a feature, but someone suggested on the general list
> that it's a bug.
Hi all,
Could someone let me know if omission of the closing php tag from a
source file without generating an error is a bug or a feature? I've
always thought it a feature, but someone suggested on the general list
that it's a bug.
Thanks in advance,
Rob.
--
.
Quoting Sebastian Bergmann <[EMAIL PROTECTED]>:
> A while ago I posted [1] a script that performed some micro-benchmarks
> on PHP.
>
> I have now refined this benchmark by splitting the monolithic script
> into one script per micro-benchmark thus performing each benchmark with
>
A while ago I posted [1] a script that performed some micro-benchmarks
on PHP.
I have now refined this benchmark by splitting the monolithic script
into one script per micro-benchmark thus performing each benchmark with
a fresh PHP interpreter.
The benchmark "suite" is available at
