PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (784 total including feature requests)
===[*General Issues]==
27372 Verified parse error loading browscap.ini at apache startup (new parser
required)
===
PHP 5 Bug Database summary - http://bugs.php.net
Num Status Summary (419 total including feature requests)
===[*Configuration Issues]
29971 Open variables_order behaviour
===[*General Issues
Guys,
I'd like to revert the fix for bug #31672 (" is not considered
closing tag if preceded by one-line comment"). While theoretically
correct, I'd rather resolve it by fixing the docs.
The reason is simple - unlike ?> and %>, the string "" is very
much likely to appear inside one line commen
Good point, +1 for revert.
Ilia
Zeev Suraski wrote:
Guys,
I'd like to revert the fix for bug #31672 (" is not considered
closing tag if preceded by one-line comment"). While theoretically
correct, I'd rather resolve it by fixing the docs.
The reason is simple - unlike ?> and %>, the string "" i
I very much agree with this. It's very common to output JavaScript via
PHP, and that also uses the tags...so...
Ilia Alshanetsky wrote:
Good point, +1 for revert.
Ilia
Zeev Suraski wrote:
Guys,
I'd like to revert the fix for bug #31672 (" is not
considered closing tag if preceded by one-line co
Hello Zeev,
i do not think this is a good excuse for ignoring xml compliance.
marcus
Monday, March 7, 2005, 3:10:57 PM, you wrote:
> Guys,
> I'd like to revert the fix for bug #31672 (" is not considered
> closing tag if preceded by one-line comment"). While theoretically
> correct, I'd ra
A user was asking about why he could perform statements such as:
$db = mysql_connect('localhost') or die('Unable to connect to database
server');
But not:
$db = new mysqli('localhost') or throw('Unable to connect to database
server');
The short answer, obviously, is that throw just doesn't beha
Hello Sara,
patch looks correct anyway Andi or Zeev is needed here
Monday, March 7, 2005, 11:13:30 PM, you wrote:
> A user was asking about why he could perform statements such as:
> $db = mysql_connect('localhost') or die('Unable to connect to database
> server');
> But not:
> $db = new my
Hey Sara,
Nothing to ridicule but there's a good reason that currently throw is a
statement. It has to do with us not being able to clean up properly when
we're within an expression as far as memory leaks, reference counting and
other locks are concerned.
Theoretically your patch could be applie
> Nothing to ridicule but there's a good reason that currently throw is a
> statement. It has to do with us not being able to clean up properly when
> we're within an expression as far as memory leaks, reference counting and
> other locks are concerned.
>
Ah, that makes perfect sense. With exit
At 20:38 07/03/2005, Marcus Boerger wrote:
Hello Zeev,
i do not think this is a good excuse for ignoring xml compliance.
I don't exactly follow what you're saying - can you elaborate?
Zeev
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
11 matches
Mail list logo
