Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77851
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain basereality.com from 74.125.82.50 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAJ26g5R6tAayBRHAdqJ=744miFDqdM2Yv4c34p2Hogm+p=W0Bg@mail.gmail.com>
References: <CAF+90c-7w1fLqmffYvPRhmtt8rzESEpSmW8vfMD-YfLt1mG_8w@mail.gmail.com>
	<543320AB.4070606@sugarcrm.com>
	<CAF+90c9+0+3TLKNdF=dnZ+OJb1UTNfeQ=ohMBrtJF=ZDXbZ23A@mail.gmail.com>
	<CAJ26g5R6tAayBRHAdqJ=744miFDqdM2Yv4c34p2Hogm+p=W0Bg@mail.gmail.com>
Date: Fri, 10 Oct 2014 13:52:10 +0100
Message-ID: <CA+kxMuTTg5tuLSQtRieDoSp+g9HFY+5DyX9Tv1wZRueTLWMS7w@mail.gmail.com>
To: Patrick Schaaf <bof@bof.de>
Cc: Nikita Popov <nikita.ppv@gmail.com>, internals <internals@lists.php.net>, 
	Stas Malyshev <smalyshev@sugarcrm.com>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Exceptions in the engine
From: danack@basereality.com (Dan Ackroyd)

Patrick wrote:
> I would love to be able to catch, at toplevel. with an error handler or
> otherwise, both the memory limits exceeded and time limit exceeded cases.

+1, as the kids today say.

I don't think that it should require any new code - we already have
the ability to extend the memory limit dynamically:

ini_set('memory_limit', (ini_get('memory_limit')+1).'M');

And similarly for set_time_limit().

Having the ability to catch these types of errors and do whatever is
required to exit the program cleanly, is far superior to having a
fatal error.

cheers
Dan