On Mon, Mar 7, 2011 at 10:49 PM, Ferenc Kovacs i...@tyrael.hu wrote:
From the sideline:
it's hard to belive that there are no one else with opinion on this matter.
I don't want to take sides because I don't have the necessary knowledge
about the matter, but maybe it would be a good idea to
Could set_time_limit() be changed in such a way that it triggers a
catchable fatal error instead of a fatal error? Thanks!
--
Sebastian BergmannCo-Founder and Principal Consultant
http://sebastian-bergmann.de/ http://thePHP.cc/
--
PHP Internals -
hi,
is not the goal of this setting to prevent that a script runs longer
than a given time? A catchable error will prevent that to happen.
On Tue, Mar 8, 2011 at 2:05 PM, Sebastian Bergmann sebast...@php.net wrote:
Could set_time_limit() be changed in such a way that it triggers a
catchable
Hi,
Would pcntl_alarm() work?
Jared
-Original Message-
From: Sebastian Bergmann [mailto:sebast...@php.net]
Sent: 08 March 2011 13:06
To: internals@lists.php.net
Subject: [PHP-DEV] Make set_time_limit() timeout a catchable
fatal error
Could set_time_limit() be changed in
On 2011-03-08, Pierre Joye pierre@gmail.com wrote:
On Mon, Mar 7, 2011 at 10:49 PM, Ferenc Kovacs i...@tyrael.hu wrote:
From the sideline:
it's hard to belive that there are no one else with opinion on this matter.
I don't want to take sides because I don't have the necessary knowledge
On Tue, Mar 8, 2011 at 4:46 PM, Matthew Weier O'Phinney
weierophin...@php.net wrote:
As a developer, in many cases I'd prefer something incomplete and limited in
support to nothing at all. I've been bitten by the same issue Stas describes,
and having a way to tie into touch and chmod in my
On Tue, Mar 8, 2011 at 4:46 PM, Matthew Weier O'Phinney
weierophin...@php.net wrote:
and having a way to tie into touch and chmod in my stream wrappers would be
incredibly useful -- even if it won't work with _every_ stream.
My point was not that it won't work with any stream, obviously. But
**
On 08/03/11 15:46, Matthew Weier O'Phinney wrote:
On 2011-03-08, Pierre Joye pierre@gmail.com wrote:
On Mon, Mar 7, 2011 at 10:49 PM, Ferenc Kovacs i...@tyrael.hu wrote:
From the sideline:
it's hard to belive that there are no one else with opinion on this matter.
I don't want to
On Tue, Mar 8, 2011 at 4:59 PM, James Butler
james.but...@edigitalresearch.com wrote:
**
On 08/03/11 15:46, Matthew Weier O'Phinney wrote:
On 2011-03-08, Pierre Joye pierre@gmail.com wrote:
On Mon, Mar 7, 2011 at 10:49 PM, Ferenc Kovacs i...@tyrael.hu wrote:
From the sideline:
it's
On Tue, Mar 8, 2011 at 1:55 PM, Pierre Joye pierre@gmail.com wrote:
On Mon, Mar 7, 2011 at 10:49 PM, Ferenc Kovacs i...@tyrael.hu wrote:
From the sideline:
it's hard to belive that there are no one else with opinion on this
matter.
I don't want to take sides because I don't have the
On Tue, Mar 8, 2011 at 5:08 PM, Ferenc Kovacs i...@tyrael.hu wrote:
if you have a better alternative which is viable, then I would support that.
otherwise I wouldn't support the all-or-nothing approach.
thats like if we couldn't add pecl/phpize until it works on every supported
On Tue, Mar 8, 2011 at 5:15 PM, Pierre Joye pierre@gmail.com wrote:
On Tue, Mar 8, 2011 at 5:08 PM, Ferenc Kovacs i...@tyrael.hu wrote:
if you have a better alternative which is viable, then I would support
that.
otherwise I wouldn't support the all-or-nothing approach.
thats like if
Hi!
implemantions/features or breaking compatibility? There is no need to
hurry with that only because it suddenly became very important for a
couple of you. Let think before coding, once, would rock :)
If not hurrying means sitting and doing nothing until a better
solution magically emerges
On Tue, Mar 8, 2011 at 6:37 PM, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
implemantions/features or breaking compatibility? There is no need to
hurry with that only because it suddenly became very important for a
couple of you. Let think before coding, once, would rock :)
If not
On 3/8/11 9:40 AM, Pierre Joye wrote:
On Tue, Mar 8, 2011 at 6:37 PM, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
implemantions/features or breaking compatibility? There is no need to
hurry with that only because it suddenly became very important for a
couple of you. Let think before
Either that or it should be spun off into its own RFC. I have no idea how to do
either.
From: Martin Scotta [mailto:martinsco...@gmail.com]
Sent: Thursday, March 03, 2011 12:09 PM
To: Jarrod Nettles
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Class Access Modifiers
I'm writing a RFC
Although it doesn't let you recover from a timeout, you could use
register_shutdown_function to gracefully exit after a fatal error.
register_shutdown_function(function(){
$error = error_get_last();
if($error $error['type'] === E_ERROR){
echo 'PHAIL! Oh noes, something went
17 matches
Mail list logo
