with more grace? I feel that
high level language interpreter should not crash its process
whatever I do in the php code. Throwing a stack overflow / memory exausted
exception would make it much easier to debug.
Cheers,
Milan
--
Best regards,
speedy
l storage could be done via normal containers, and global via
thread-safe ones.
I'm not sure how could that be exposed on the language level, though.
--
Best regards,
speedymailto:speedy.s...@gmail.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsu
d, then the overhead should go large because of the
> deep copy.
Note that could be optimized by implementing copy on write (with
properly placed hooks and shared data) between contexts - would save tons
of memory and speed up the thread creation by an order of magnitude.
> Moriyoshi
t it is a can of worms which can
easily shoot you in the foot ;) Some kind of php.ini or #pragma-alike
threading directive for the programmer to "unlock" it him/herself
would be really smart to be had.
> --
> Wbr,
> Antony Dovgal
> ---
> http://pinba.org - realtime stat
ithic CLI apps, you could make a case
> for it, but that is not the sort of architecture we are going to put a
> significant amount of time into.
Yep, agreed and understood.
> -Rasmus
--
Best regards,
speedymailto:speedy.s...@gmail.com
--
PHP Internals -
Hello Rasmus,
Thursday, April 1, 2010, 5:21:55 PM, you wrote:
> On 04/01/2010 07:32 AM, speedy wrote:
>> 1. Imagine that from time to time, some background processing takes 1
>> second of CPU time - w/o multithreading, all your async operations,
>> like a
s language feature.
--
Best regards,
speedy mailto:speedy.s...@gmail.com
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
