On 14.04.2010 06:53, looyao teng wrote:
> hi, I'm a php programmer, our site use PHP's Imagemagick
> extension to process images, and this would consume a lot of
> memory under some circumstances. However, the mainstream
> PHP's memory management is really weak, so a huge amount
> of memory wou
I think my svn account is "looyao". :)
hi, I'm a php programmer, our site use PHP's Imagemagick
extension to process images, and this would consume a lot of
memory under some circumstances. However, the mainstream
PHP's memory management is really weak, so a huge amount
of memory would be consumed under high server load. What's
wors
Personally, I would strongly prefer the caller syntax my_func('a',
'b', 'c' => 'd', $e => $f) just to because
1) it's consistent with array declaration syntax
2) it allows arbitrary names for parameters, which will become the
array keys ... and can include funny characters
3) naked
Le 13 avril 2010 21:01, Zeev Suraski a écrit :
> At 21:46 13/04/2010, Christopher Jones wrote:
>
>
>> Jérôme Loyet wrote:
>>>
>>> Le 13 avril 2010 20:17, Christopher Jones
>>> a écrit :
Jérôme Loyet wrote:
>
> Hi guys,
>
> As dreamcast4 advises me in the previous FPM con
2010/4/13 Zeev Suraski :
> What he means is that it'll be implemented in the custom code responsible
> for parsing fpm.ini, and not in the ZE .ini parser which would be the layer
> below it. Implementing include() can be done at either layer. If it's
> implemented at the bottom layer (ZE) then i
At 21:46 13/04/2010, Christopher Jones wrote:
Jérôme Loyet wrote:
Le 13 avril 2010 20:17, Christopher Jones
a écrit :
Jérôme Loyet wrote:
Hi guys,
As dreamcast4 advises me in the previous FPM conversation, I just
wrote the RFC for the FPM INI syntax.
It can be read here: http://wiki.php.
This patch has been awaiting review for over a month. Is there anything
I can do to help hurry things along?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Jérôme Loyet wrote:
Le 13 avril 2010 20:17, Christopher Jones
a écrit :
Jérôme Loyet wrote:
Hi guys,
As dreamcast4 advises me in the previous FPM conversation, I just
wrote the RFC for the FPM INI syntax.
It can be read here: http://wiki.php.net/rfc/fpm/ini_syntax
Tell me what you think.
Le 13 avril 2010 20:17, Christopher Jones
a écrit :
>
>
> Jérôme Loyet wrote:
>>
>> Hi guys,
>>
>> As dreamcast4 advises me in the previous FPM conversation, I just
>> wrote the RFC for the FPM INI syntax.
>>
>> It can be read here: http://wiki.php.net/rfc/fpm/ini_syntax
>>
>> Tell me what you thi
Jérôme Loyet wrote:
Hi guys,
As dreamcast4 advises me in the previous FPM conversation, I just
wrote the RFC for the FPM INI syntax.
It can be read here: http://wiki.php.net/rfc/fpm/ini_syntax
Tell me what you think.
++ Jerome
I think the RFC should clearly state what is new generic php.
Hi Kalle,
Kalle Sommer Nielsen wrote:
Hi
2010/4/13 Dmitry Stogov :
Hi,
I've published all the patches, their description and performance evaluation
at http://wiki.php.net/rfc/performanceimprovements
The only thing I notice while browsing the patches was that you need
to add the zend_string.
Hi Jared,
Jared Williams wrote:
Hi
Wondering if there is any plans to for new serialization
method?
Not in this patch.
One of the things that igbinary does is store strings only
once, and now that the engine supports string interning natively,
seems that serialization and de
Hi Richard,
Richard Quadling wrote:
On 13 April 2010 14:53, Dmitry Stogov wrote:
Hi,
I've published all the patches, their description and performance evaluation
at http://wiki.php.net/rfc/performanceimprovements
In two words the patches give 0-20% improvement even on real-life
applications.
Hi
2010/4/13 Dmitry Stogov :
> Hi,
>
> I've published all the patches, their description and performance evaluation
> at http://wiki.php.net/rfc/performanceimprovements
The only thing I notice while browsing the patches was that you need
to add the zend_string.c and other new files to win32/build
Hi
Wondering if there is any plans to for new serialization
method?
One of the things that igbinary does is store strings only
once, and now that the engine supports string interning natively,
seems that serialization and deserialization could benefit.
Though I guess igbi
On Tue, Apr 13, 2010 at 16:21, Gerardo Benitez wrote:
> Translating the documentation
What language do you intent to translate it to?
--
Daniel Egeberg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Translating the documentation
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
I've published all the patches, their description and performance
evaluation at http://wiki.php.net/rfc/performanceimprovements
In two words the patches give 0-20% improvement even on real-life
applications.
I'm going to commit them into trunk in a week in case of no objections.
Of cou
On 12-apr-2010, at 10:20, Derick Rethans wrote:
> On Mon, 22 Mar 2010, Felix De Vliegher wrote:
>
>> On 17-mrt-2010, at 19:09, Derick Rethans wrote:
>>
>>> On Wed, 17 Mar 2010, Felix De Vliegher wrote:
>>>
On 17-mrt-2010, at 17:52, Derick Rethans wrote:
> On Wed, 17 Mar 2010, Fel
On 13.04.2010 11:44, Tjerk Anne Meesters wrote:
> Think it's also important to keep the IDE factor in mind. By just
> defining a catch-all at the end of your function declarations you
> essentially cut short any effort that could be made to have IDE code
> insight support for this language enhancem
Hello.
Here is some userland feedback:
I was following the thread closely, because I use fastcgi all the time. I
can now say for sure, that you did really good job with ini syntax - the one
you have at the moment looks and feels just perfect. And includes make it
really easy to use - it's what XM
Think it's also important to keep the IDE factor in mind. By just
defining a catch-all at the end of your function declarations you
essentially cut short any effort that could be made to have IDE code
insight support for this language enhancement.
On 4/13/10, Jordi Boggiano wrote:
> On 13.04.2010
Le 13 avril 2010 11:33, Ferenc Kovacs a écrit :
>
>> done.
>> To compare really:
>> http://www.fatbsd.com/fpm/xml.html
>> http://www.fatbsd.com/fpm/fpm_ini.html
>>
>> I made some small changes and update to RFC version 1.1
>> ++ Jerome
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing Li
> done.
> To compare really:
> http://www.fatbsd.com/fpm/xml.html
> http://www.fatbsd.com/fpm/fpm_ini.html
>
> I made some small changes and update to RFC version 1.1
> ++ Jerome
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Le 12 avril 2010 13:47, dreamcat four a écrit :
> 2010/4/12 Derick Rethans :
>> On Tue, 30 Mar 2010, Jérôme Loyet wrote:
>>
>>> As dreamcast4 advises me in the previous FPM conversation, I just
>>> wrote the RFC for the FPM INI syntax.
>>>
>>> It can be read here: http://wiki.php.net/rfc/fpm/ini_s
On 13.04.2010 01:30, Pierre Joye wrote:
> On Tue, Apr 13, 2010 at 1:28 AM, Stanislav Malyshev wrote:
>
>> I think that's the idea in general, now how it looks like - be it 'opt1' =>
>> 'no-foo' or opt1: 'no-foo' - that's the decision we need to take. I
>> personally still don't have the favorite,
At 20:08 30/03/2010, Jérôme Loyet wrote:
Hi guys,
As dreamcast4 advises me in the previous FPM conversation, I just
wrote the RFC for the FPM INI syntax.
It can be read here: http://wiki.php.net/rfc/fpm/ini_syntax
Tell me what you think.
Looks good to me.
Zeev
--
PHP Internals - PHP Run
Am 13.04.2010 09:12, schrieb Zeev Suraski:
> Dmitry's in the process of separating the different improvements into
> separate patches and improving their consistency while at it; We'll
> also work on RFC(s).
Great to hear! I'll be glad to help with testing the patches once they
are available.
At 17:32 11/04/2010, Sebastian Bergmann wrote:
Am 11.04.2010 16:21, schrieb Lukas Kahwe Smith:
> So where do we stand here?
I was wondering the same.
Dmitry's in the process of separating the different improvements into
separate patches and improving their consistency while at it; We'll
al
30 matches
Mail list logo
