Hi Daniel,
>> But, for what you're testing, that's the behavior I'd expect -- once
>> you've reached the precision of a double, you'll only get the closest
>> representation possible (and of course a 64-bit long is more precise than
>> a double since there's no floating point to represent). Al
On 31.03.2009, at 08:51, Hannes Magnusson wrote:
On Tue, Mar 31, 2009 at 04:47, Greg Beaver
wrote:
Lukas Kahwe Smith wrote:
So where are we at here?
If nobody proposes something, this will just slide by ..
I propose reserving PHP. extensions can be PHP\extname (i.e. class
PHP\Phar, or f
On 02.04.2009, at 19:33, Johannes Schlüter wrote:
Hi,
On Wed, 2009-04-01 at 20:47 -0700, Justin Martin wrote:
The update I'd like to propose is to the Zend Highlighter for PHP,
specifically related to the highlight_file and highlight_string
functions, as well as the php -s command.
I don't
Hi Matt, and everyone:
On Mon, Apr 06, 2009 at 01:00:47PM -0500, Matt Wilmas wrote:
> unless I'm missing something,
> you're talking about converting long/int to double/float. That's the
> opposite of this thread subject, which is how to convert a double to a
> long when it's out of the ran
On 07.04.2009, at 19:09, Kinch Zhang wrote:
Just a question: when will PHP 5.3 RC2 be out? we're waiting for it so
it would be good to know the schedule.
I was hoping for a release this week on Thursday. At this time it
seems unlikely that we will even release it Thursday next week. But
hi, list:
Just a question: when will PHP 5.3 RC2 be out? we're waiting for it so
it would be good to know the schedule.
Regards,
Kinch Zhang
--
"Unix is simple. It just takes a genius to understand its simplicity."
"Simplicity is the essence of happiness."
--
PHP Internals - PHP Runtime Dev
Hi,
On Tue, 2009-04-07 at 10:38 +0200, Lukas Kahwe Smith wrote:
> > Currently you cannot serialize a closure. That certainly makes sense.
[...]
> I guess its a dont go there thing, as you also run into trouble with
> "use"-d variables.
In the long run, I guess, we should try to reach it. Ignor
vouched! He will be contributing to the benchmark creation project.
Can someone please take care of his account + karma for the
'php-benchmarks'
module?
Done
Thank you Derick!
Nuno
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, 7 Apr 2009, Nuno Lopes wrote:
> vouched! He will be contributing to the benchmark creation project.
> Can someone please take care of his account + karma for the 'php-benchmarks'
> module?
Done
Derick
--
http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org
twitter: der
vouched! He will be contributing to the benchmark creation project.
Can someone please take care of his account + karma for the 'php-benchmarks'
module?
Thanks,
Nuno
- Original Message -
Contributing benchmarks
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, v
On 31.03.2009, at 20:36, Dmitry Stogov wrote:
Hi Basant,
I've updated you patch for 5.3 (attached, don't forget to regenerate
zend_vm_execute.h). 5.2 is closed for such changes anyway and I
don't think the patch should be applied into 5.3 too, because it is
in RC stage.
I got ~10% spee
Hi,
@Matt: thx for getting back to me on this.
In general all the technical details are way over my head. What
worries me is that we are going back and forth with these changes. It
seems there is a pretty large "trail and error" part to these changes.
So for the most part at this stage I d
Although this may open a lot of pitfalls, I'd support the idea to
serialize Closures.
My concern is about recovering a Closure from a user-persisted state.
People are able to do weird things, and we should be aware of that.
Just need to keep in mind of a dictate that says: "Never underestimate
the
On 07.04.2009, at 09:55, Richard Quadling wrote:
Hi.
Currently you cannot serialize a closure. That certainly makes sense.
But would it be possible/feasible that a closure could be serialized
if the value returned was the byte code used by the engine to execute
the compiled closure?
Or is th
Hi.
Currently you cannot serialize a closure. That certainly makes sense.
But would it be possible/feasible that a closure could be serialized
if the value returned was the byte code used by the engine to execute
the compiled closure?
Or is this one of the "don't go there" ideas I sometimes get?
15 matches
Mail list logo
