Just found out that MySQL uses the same implicit conversion precedence on
SQL clauses. That shows me that possibly exists some "higher order" rule
that states this consistency, and changing that is outside the scope of PHP.
On Thu, Jun 13, 2013 at 9:20 AM, Stuart Dallas wrote:
> On 13 Jun 2013,
On 13 Jun 2013, at 12:27, BUSCHKE Daniel wrote:
> Hi,
>
>> It gives up when it finds a non-numeric character (as the documentation
>> would tell you)
>
> Why is PHP doing that? I know it works as designed and I know it is
> documented like this but that does not mean that it is a good feature
On 13/06/13 08:59, BUSCHKE Daniel wrote:
Hi all,
I want to start a discussion about a PHP behaviour that drives me crazy for
years. For the beginning I would like you to guess what the result of the
following snippet will be:
var_dump('PHP' == 0);
I know the difference of == and === but the r
Sorry missed to post list as well
Hi Daniel,
here is wild goose
i assume you have 3 x =
in your "problem" formulation
which could possibly result in the akward standard C mixup;
the rightmost = first parsed and resulting in an ASSIGMENT to the variable
with that value,
the comes the parsing of
4 matches
Mail list logo
