On 19 May 2010 22:18, Alban LEROUX wrote:
> On 2010-05-19 14:04:13 +0200, Ferenc Kovacs said:
>
>> On Wed, May 19, 2010 at 1:49 PM, Christian Schneider
>> wrote:
>>
>>> fqqdk wrote:
How about extending the usage of the 'final' keyword to support a
>>>
>>> java-like
syntax?
Hello !
I have a problem with php 5.3.2 under FreeBSD 7/8 with configure option
--enable-zend-multibyte and phar support.
Then i use this option, phar does not work correctly.
No seg fault, no crash, just... nothing or cabalistic letter in output
of my script.
To solve the problem, recompilati
On 05/20/2010 11:28, Frederic Hardy wrote:
I have a problem with php 5.3.2 under FreeBSD 7/8 with configure
option --enable-zend-multibyte and phar support.
Then i use this option, phar does not work correctly.
No seg fault, no crash, just... nothing or cabalistic letter in output
of my script.
Dmitry Stogov wrote:
> Hi,
>
> I'm proposing another optimisation technique implementation for PHP
> which makes up to 20% speed up on synthetic tests and up to 8% speed up
> on real-life applications.
>
> The technique is similar to "inline caches" which is very popular in JIT
> compilers for o
I know this issue has been seen before, but I hope to do something about it.
$json = '1234567890123456789';
$x = json_decode($json);
/* $x is now a float *aproximately*
* equal to the original value
*/
For database indexes, being off by one can be disasterous for
application flow, so I'd like
hi Sara,
The idea sounds sane, until we have big integer support :)
Only one thing, I would suggest to use JSON_BIGINT_AS_STRING instead,
more clear about its effect.
Cheers,
On Thu, May 20, 2010 at 9:50 PM, Sara Golemon wrote:
> I know this issue has been seen before, but I hope to do somethi
Sara,
Could you not treat a very large integer as a double? We do that in a few
areas of the code already.
On Thu, May 20, 2010 at 3:50 PM, Sara Golemon wrote:
> I know this issue has been seen before, but I hope to do something about
> it.
>
> $json = '1234567890123456789';
> $x = json_decode(
Ilia Alshanetsky wrote:
Could you not treat a very large integer as a double? We do that in a few
areas of the code already.
Treating it as a double is exactly what json_decode() *currently* does,
and it's the problem I'm trying to work around by leaving it in string form.
When a large intege
Hi Jones,
Christopher Jones wrote:
Dmitry Stogov wrote:
> Hi,
>
> I'm proposing another optimisation technique implementation for PHP
> which makes up to 20% speed up on synthetic tests and up to 8% speed up
> on real-life applications.
>
> The technique is similar to "inline caches" wh
