On Thu, Dec 24, 2009 at 9:28 AM, Michael Shadle wrote:
> On Wed, Dec 23, 2009 at 5:12 PM, Mikko Koppanen wrote:
>> Hi,
>>
>> I think this is the feature (in trunk currently):
>>
>> http://svn.php.net/viewvc?view=revision&revision=28287
>
> This is not the same, this is just an additional way to s
On Wed, Dec 23, 2009 at 5:12 PM, Mikko Koppanen wrote:
> Hi,
>
> I think this is the feature (in trunk currently):
>
> http://svn.php.net/viewvc?view=revision&revision=28287
This is not the same, this is just an additional way to still have
static dirs defined only at compile time, or maybe envir
On Thu, Dec 24, 2009 at 12:23 AM, Pierre Joye wrote:
> So what you need is multiple ini dirs, not actually include. I think
> there is a patch somewhere for this feature, or it may even be already
> in. If not, that could be something useful.
Hi,
I think this is the feature (in trunk currently):
On Wed, Dec 23, 2009 at 2:23 PM, Pierre Joye wrote:
> So what you need is multiple ini dirs, not actually include. I think
> there is a patch somewhere for this feature, or it may even be already
> in. If not, that could be something useful.
To me, it solves all of the usage models currently pro
Hi!
As of now, zend_parse_method_parameters_ex does ignore the ex-flags if
called in a procedural context.
NB: Calling it in a procedural context is explicitely handled in the
code! It's not a false use of the function.
I suppose, the body was copied from zend_parse_method_parameters and the
"
On Wed, Dec 23, 2009 at 10:25 PM, Michael Shadle wrote:
> On Wed, Dec 23, 2009 at 10:47 AM, Pierre Joye wrote:
>
>> Please tell me one benefit except "we support include"? I don't see
>> any. The extra files are still there, they will be loaded too, etc.
>
> Instead of a -single location- being d
On Wed, Dec 23, 2009 at 10:47 AM, Pierre Joye wrote:
> Please tell me one benefit except "we support include"? I don't see
> any. The extra files are still there, they will be loaded too, etc.
Instead of a -single location- being defined at compile time or
execution of PHP time, this allows it N
On 24-Dec-2009, at 2:47, Pierre Joye wrote:
On Wed, Dec 23, 2009 at 7:20 PM, Michael Shadle
wrote:
On Wed, Dec 23, 2009 at 10:13 AM, Mikko Koppanen
wrote:
Hello,
I think you can use PHP_INI_SCAN_DIR environment variable which
should
work runtime as well.
still seems a bit archaic.
On Wed, Dec 23, 2009 at 7:20 PM, Michael Shadle wrote:
> On Wed, Dec 23, 2009 at 10:13 AM, Mikko Koppanen wrote:
>
>> Hello,
>>
>> I think you can use PHP_INI_SCAN_DIR environment variable which should
>> work runtime as well.
>
> still seems a bit archaic. i don''t see any reason why include sup
On Wed, Dec 23, 2009 at 10:13 AM, Mikko Koppanen wrote:
> Hello,
>
> I think you can use PHP_INI_SCAN_DIR environment variable which should
> work runtime as well.
still seems a bit archaic. i don''t see any reason why include support
can't be added in php.ini. it will probably wind up becoming
2009/12/23 Michael Shadle :
> i am fine with both too. i just think it's sorely lacking to be able
> to do it any other time than at compile time -and- that only provides
> you one location.
>
> could be very powerful to allow for any location to be scanned for ini files.
>
Hello,
I think you can
i am fine with both too. i just think it's sorely lacking to be able
to do it any other time than at compile time -and- that only provides
you one location.
could be very powerful to allow for any location to be scanned for ini files.
2009/12/23 Tjerk Meesters :
> On 23-Dec-2009, at 21:47, Johan
On Wed, December 23, 2009 11:21 am, Rasmus Lerdorf wrote:
> Richard Quadling wrote:
>> 2009/12/23 Rasmus Lerdorf :
>>> Can anyone think of a situation where you actually want our current
>>> ignore_user_abort=false setting for the cli sapi?
>>
>> I would say that the default setting is pretty impor
Richard Quadling wrote:
> 2009/12/23 Rasmus Lerdorf :
>> Can anyone think of a situation where you actually want our current
>> ignore_user_abort=false setting for the cli sapi?
>
> I would say that the default setting is pretty important as pressing
> CTRL+C (at least on windows) is the quickest
No, ignore_user_abort has no effect on what the process does when it
receives a SIGHUP, so that isn't relevant.
-Rasmus
Tjerk Anne Meesters wrote:
> Maybe to make it respond to SIGHUP signals? Not exactly sure whether
> that would constitute as user_abort though.
>
> On 12/23/09, Rasmus Lerdorf
On Wed, Dec 9, 2009 at 2:04 AM, Stanislav Malyshev wrote:
> Hi!
>
> I think stream_resolve_include_path() should be changed to work through
> zend_resolve_path, in any case. Also, what is the reason it can't be in 5.3
> too?
> I'd like to both fix stream_resolve_include_path() and get it into 5.3,
2009/12/23 Rasmus Lerdorf :
> Can anyone think of a situation where you actually want our current
> ignore_user_abort=false setting for the cli sapi?
I would say that the default setting is pretty important as pressing
CTRL+C (at least on windows) is the quickest way of killing a PHP cli
based scr
On 23-Dec-2009, at 21:47, Johannes Schlüter
wrote:
On Wed, 2009-12-23 at 04:40 -0800, Michael Shadle wrote:
NOTE: I just remembered there -is- a config-file-scan-dir option at
compile time. However, what about doing away with this and making it
inline in php.ini, the syntax can match mysql,
On Wed, 2009-12-23 at 04:40 -0800, Michael Shadle wrote:
> NOTE: I just remembered there -is- a config-file-scan-dir option at
> compile time. However, what about doing away with this and making it
> inline in php.ini, the syntax can match mysql, as it uses ini files as
> well.
I think the --with-
NOTE: I just remembered there -is- a config-file-scan-dir option at
compile time. However, what about doing away with this and making it
inline in php.ini, the syntax can match mysql, as it uses ini files as
well.
This mainly will help with programatically creating PHP-FPM pool
config files, but c
Hi!
As of now, zend_parse_method_parameters_ex does ignore the ex-flags if
called in a procedural context.
NB: Calling it in a procedural context is explicitely handled in the
code! It's not a false use of the function.
I suppose, the body was copied from zend_parse_method_parameters and the
"fl
Maybe to make it respond to SIGHUP signals? Not exactly sure whether
that would constitute as user_abort though.
On 12/23/09, Rasmus Lerdorf wrote:
> Can anyone think of a situation where you actually want our current
> ignore_user_abort=false setting for the cli sapi?
>
> -Rasmus
>
> --
> PHP In
Can anyone think of a situation where you actually want our current
ignore_user_abort=false setting for the cli sapi?
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
23 matches
Mail list logo
