Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87318
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.170 as permitted sender)
To: internals@lists.php.net
References: <550FA2ED.6080000@gmail.com>
 <CADR=R-gtCy7Vi7Y15jx+SYWX3aEB6TN3WGJPAqqQ4tO__SWqQw@mail.gmail.com>
Message-ID: <55B63C55.20903@gmail.com>
Date: Mon, 27 Jul 2015 15:12:37 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <CADR=R-gtCy7Vi7Y15jx+SYWX3aEB6TN3WGJPAqqQ4tO__SWqQw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Serializing exceptions
From: rowan.collins@gmail.com (Rowan Collins)

Stas Malyshev wrote on 27/07/2015 08:08:
> Since discussion on this did not lead to a definite conclusion, but I did
> not hear from anybody that they need serialized exceptions, and we keep
> getting bug reports about exception serialization and various issues
> triggered by it, I propose this change:
> https://github.com/php/php-src/pull/1442

I agree that this is better than the status quo - although I would still 
prefer stripping out the 'args' from the exception backtrace, which has 
other benefits for predictable destructors etc.

Out of interest, is there any way to over-ride a denied serialization 
like this, using __sleep or Serializable? At the moment, you can create 
serializable sub-classes of exception, and retain a summarised copy of 
the backtrace: http://3v4l.org/IHPI5

It's not a big deal either way - in the rare cases where serialization 
of exception data is necessary, you could just write a wrapper to 
extract the public details - but I'm interested if my current hack will 
be adaptable if this change is applied.

Regards,
-- 
Rowan Collins
[IMSoP]