Re: [PHP-DEV] Intl extension class MessageFormatter instantiation returns NULL

2009.12.09 22:38 Chris Stockton rašė: > Hello, > > I am trying to use ChoiceFormat in the Intl extension. When I try to > do something like: > > $r = new MessageFormatter("en", "There are {0≤are no files|1≤is one > file|1 // $r is NULL > > This may be a incorrect use, but my thought is that regardl

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

2009/12/9 Olivier Hill : > Hello Michael, > > Are you talking about this? > > --with-config-file-scan-dir=... > > http://www.radwin.org/michael/blog/2006/07/phpini_hacks_withconfigfil.html oh, duh - I guess I am. Except it would be nice to have it inside of php.ini itself and not defined at compil

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Hello Michael, Are you talking about this? --with-config-file-scan-dir=... http://www.radwin.org/michael/blog/2006/07/phpini_hacks_withconfigfil.html Regards, Olivier 2009/12/9 Michael Shadle : > 2009/12/9 Jérôme Loyet : > >> is there a way to include files ? >> include /etc/php-fpm/*.conf ? w

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

2009/12/9 Jérôme Loyet : > is there a way to include files ? > include /etc/php-fpm/*.conf ? with one file per worker for example ? > > I think adding include to ini should not be a problem if it's not already > done. I would love to see the php ini file support includes like MySQL does. Probab

Re: [PHP-DEV] [PATCH] session_set_save_handler(class)

Hi, On Wed, Dec 9, 2009 at 11:16 PM, Stanislav Malyshev wrote: > It now raises an error rather than segfaulting if the user module is >> selected but no handler has been registered. This should really halt >> execution which it doesn't at the moment but I'll raise that separately. >> > > I'd say

RE: [PHP-DEV] Intl extension class MessageFormatter instantiation returns NULL

> -Original Message- > From: Chris Stockton [mailto:chrisstockto...@gmail.com] > Sent: 09 December 2009 20:39 > To: PHP Developers Mailing List > Subject: [PHP-DEV] Intl extension class MessageFormatter > instantiation returns NULL > > Hello, > > I am trying to use ChoiceFormat in th

Re: [PHP-DEV] [PATCH] session_set_save_handler(class)

Hi! 2. What happens if session module is set to "user" in configuration - what old_mod will be then and how this patch will work? It now raises an error rather than segfaulting if the user module is selected but no handler has been registered. This should really halt execution which it

Re: [PHP-DEV] PHP 5.3.1 reference parameter regression

Hi! Test cases can be found here:. It seems to me that a special case would be needed to restore the behaviour seen in PHP 5.3.0. I'll check it out, seems to be valid use case, we should find some solution for that. I've tried emailing stas but I didn'

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Le 9 décembre 2009 23:25, Tjerk Anne Meesters a écrit : > Hi, > > ini files can be split, so it doesn't all have to be inside one > monolithic php.ini is there a way to include files ? include /etc/php-fpm/*.conf ? with one file per worker for example ? I think adding include to ini should not b

Re: [PHP-DEV] [PATCH] session_set_save_handler(class)

On Wed, Dec 9, 2009 at 2:35 AM, Stanislav Malyshev wrote: > Hi! > > > By extending the new internal class SessionHandler, users can wrap or >> override methods of whatever session handler is in use, or implement a >> complete custom handler. >> > > Hi, Thanks very much for your feedback, I've m

[PHP-DEV] PHP 5.3.1 reference parameter regression

Since 5.3.1 it's impossible to have a reference parameter passed to a __call() function. This is apparently due to the bugfix committed by stas as shown here: Test cases can be foun

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Hi, ini files can be split, so it doesn't all have to be inside one monolithic php.ini I agree that repetition doesn't look nice; it would be nice to have something like: [fpm.worker.worker1] listen = 127.0.0.1:1900 uid = webservice Etc. Didn't really pay attention to those pool settings, but

Re: [PHP-DEV] A patch for bug 44331

On Wed, 2009-12-09 at 22:54 +0100, Florian Anderiasch wrote: > > --- ext/json/json.c.orig2009-12-09 22:15:33.0 +0100 > +++ ext/json/json.c 2009-12-09 22:48:04.0 +0100 > @@ -42,6 +42,7 @@ > #define PHP_JSON_HEX_APOS (1<<2) > #define PHP_JSON_HEX_QUOT (1<<3) >

Re: [PHP-DEV] A patch for bug 44331

Ignore me, it's fine and I'll apply it soon. S On 9 Dec 2009, at 21:58, Scott MacVicar wrote: > The JSON API is exported and can't change it as it breaks the ABI. I know the > memcached extension uses this. > > I'll look into adding something similar this week, thanks for the patch. > > S >

Re: [PHP-DEV] A patch for bug 44331

The JSON API is exported and can't change it as it breaks the ABI. I know the memcached extension uses this. I'll look into adding something similar this week, thanks for the patch. S On 9 Dec 2009, at 21:54, Florian Anderiasch wrote: > -- PHP Internals - PHP Runtime Development Mailing Lis

[PHP-DEV] A patch for bug 44331

Hi there, I've tried to come up with a solution for Formatting option for json_encode http://bugs.php.net/bug.php?id=44331 Any comments are highly welcome :) the patch is against the PHP_5_3 branch as HEAD changes quite some unicode stuff. Greetings, Florian --- ext/json/json.c.orig2009

Re: [PHP-DEV] Breaking APIs for no good reason is a bad thing. (tm)

On 12/09/2009 08:37 PM, Sara Golemon wrote: Now, I'll take some blame here for not being involved over the past couple years and having not noticed this inanity sooner, but could someone explain this cluster-f? It's also bad thing to abandon code like some people tend to do. And to ignore bug r

[PHP-DEV] Intl extension class MessageFormatter instantiation returns NULL

Hello, I am trying to use ChoiceFormat in the Intl extension. When I try to do something like: $r = new MessageFormatter("en", "There are {0≤are no files|1≤is one file|1http://www.php.net/unsub.php

Re: [PHP-DEV] Opcode EXT_FCALL_BEGIN and EXT_FCALL_END?

Hi! So, why not remove them? :) Why remove them? They don't hurt anyone. They might be also usable for something like static analysis (to know when fcall begins and ends), or maybe somebody out there is using them for something else. -- Stanislav Malyshev, Zend Software Architect s...@zen

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Le 9 décembre 2009 20:56, Michael Shadle a écrit : > 2009/12/9 Jérôme Loyet : > >> do you mean that it would be included in the global php.ini file ? I >> never imagine that. For me it's an independant conf file >> (/etc/php-fpm.conf for example). > > correct. I don't see any reason for a differen

Re: [PHP-DEV] Opcode EXT_FCALL_BEGIN and EXT_FCALL_END?

Stanislav Malyshev wrote: > I think those appeared before execute() was overridable, so newer code > doesn't have to use it. So, why not remove them? :) -- Sebastian BergmannCo-Founder and Principal Consultant http://sebastian-bergmann.de/ http://th

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

2009/12/9 Jérôme Loyet : > do you mean that it would be included in the global php.ini file ? I > never imagine that. For me it's an independant conf file > (/etc/php-fpm.conf for example). correct. I don't see any reason for a different configuration file anymore -- PHP Internals - PHP Runtime

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Le 9 décembre 2009 20:44, Michael Shadle a écrit : > I see it more like: > > fpm.global.daemonize = yes > fpm.global.error_log = /var/log/php-fpm.log > > or skip global: > > fpm.daemonize = yes > fpm.error_log = /var/log/php-fpm.log > > > for each worker pool: > > fpm.worker1.name = pool1 > fpm.wo

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

I see it more like: fpm.global.daemonize = yes fpm.global.error_log = /var/log/php-fpm.log or skip global: fpm.daemonize = yes fpm.error_log = /var/log/php-fpm.log for each worker pool: fpm.worker1.name = pool1 fpm.worker1.address = 127.0.0.1:9000 ; or socket fpm.worker1.uid = www-data fpm.wo

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Le 9 décembre 2009 19:17, Michael Shadle a écrit : > 2009/12/9 Zeev Suraski : > >> We should be using INI unless there are compelling reasons against it, now >> that this project becomes a part of the PHP source tree.  As far as I can >> tell there are no such compelling reasons and it can actuall

Re: [PHP-DEV] Opcode EXT_FCALL_BEGIN and EXT_FCALL_END?

Hi! Are you guys using those in Zend Debugger? Because in Xdebug I found them utterly useless (not EXT_STMT, which I do use). Instead of using EXT_FCALL_* I just do the triggers in the overloaded zend_execute. I think those appeared before execute() was overridable, so newer code doesn't have

[PHP-DEV] Breaking APIs for no good reason is a bad thing. (tm)

Now, I'll take some blame here for not being involved over the past couple years and having not noticed this inanity sooner, but could someone explain this cluster-f? http://svn.php.net/viewvc/php/php-src/branches/PHP_5_3/Zend/zend_API.h?r1=268281&r2=269153 This breaks the existing module API bec

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

2009/12/9 Zeev Suraski : > We should be using INI unless there are compelling reasons against it, now > that this project becomes a part of the PHP source tree.  As far as I can > tell there are no such compelling reasons and it can actually map quite > nicely into INI, hence, that's what we shoul

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

At 19:44 09/12/2009, Jérôme Loyet wrote: So let have the question another way: Do we keep XML or do we switch to something else ? If so, which format ? I and some others think xml is not appropriate here because of the complexity. So I do think there is a need to change. INI or other ? INI is u

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

On 09.12.2009, at 20:44, Jérôme Loyet wrote: > Le 9 décembre 2009 17:16, Pierre Joye a écrit : >> hi, >> >> 2009/12/9 Jérôme Loyet : >> > We already discussed pros/cons of the two solutions. But why don't we > allow several syntaxes ? And let the end user to choose the better one >

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Le 9 décembre 2009 17:16, Pierre Joye a écrit : > hi, > > 2009/12/9 Jérôme Loyet : > We already discussed pros/cons of the two solutions. But why don't we allow several syntaxes ? And let the end user to choose the better one for its need ? >>> >>> No. Thank you. >>> EOD >>> >> >> a

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Hi! I think multiple syntaxes is an unnecessary complication, and they don't serve any useful purpose - neither of those syntaxes allow you to do something important that others don't. -- Stanislav Malyshev, Zend Software Architect s...@zend.com http://www.zend.com/ (408)253-8829 MSN: s...

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

hi, 2009/12/9 Jérôme Loyet : >>> We already discussed pros/cons of the two solutions. But why don't we >>> allow several syntaxes ? And let the end user to choose the better one >>> for its need ? >> >> No. Thank you. >> EOD >> > > and why of that ? Why is it already EOD wihtout arguing ? php-fpm

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Hi, I know little aobut FPM but: On Wed, 2009-12-09 at 15:55 +0100, Jérôme Loyet wrote: > We already discussed pros/cons of the two solutions. But why don't we > allow several syntaxes ? And let the end user to choose the better one > for its need ? No. Several syntaxes makes testing harder, is

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

Le 9 décembre 2009 15:57, Antony Dovgal a écrit : > On 09.12.2009 17:55, Jérôme Loyet wrote: >> Hi guys, >> >> I start a new thread about the syntax that should be used in php-fpm >> to replace xml. >> >> As discussed before, there is different point on view on this subject: >> - INI to stay in th

Re: [PHP-DEV] [PHP-FPM] syntax of configuration file

On 09.12.2009 17:55, Jérôme Loyet wrote: > Hi guys, > > I start a new thread about the syntax that should be used in php-fpm > to replace xml. > > As discussed before, there is different point on view on this subject: > - INI to stay in the PHP philosophy / practicals > - nginx because it was the

[PHP-DEV] [PHP-FPM] syntax of configuration file

Hi guys, I start a new thread about the syntax that should be used in php-fpm to replace xml. As discussed before, there is different point on view on this subject: - INI to stay in the PHP philosophy / practicals - nginx because it was the will of the original authors We already discussed pros/

Re: [PHP-DEV] Opcode EXT_FCALL_BEGIN and EXT_FCALL_END?

On Mon, 7 Dec 2009, Stanislav Malyshev wrote: > > I am wondering what the opcode EXT_FCALL_BEGIN and EXT_FCALL_END is used > > for? > > When php is in "extended opcode" mode (usually used by debuggers) these > opcodes are generated by the compiler before entering and after exiting > function call