Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85417
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <550FA2ED.6080000@gmail.com>
References: <550FA2ED.6080000@gmail.com>
Date: Mon, 23 Mar 2015 01:31:34 -0400
Message-ID: <CA+sv8zAzq=WEohJmrzaRev+F736HoCKY1Dfq7Cpv8J7FQZ=Yag@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec511e116b1d32e0511edfa7d
Subject: Re: [PHP-DEV] Serializing exceptions
From: jrbasso@gmail.com (Juan Basso)

--bcaec511e116b1d32e0511edfa7d
Content-Type: text/plain; charset=UTF-8

Maybe you can implement the __sleep method and just return the documented
attributes (message, code, file, line).

Not perfect, but probably more useful than throw an exception, specially if
the exception is something that is the attribute of some object that is
being serialized.

Juan Basso
On Mar 23, 2015 1:22 AM, "Stanislav Malyshev" <smalyshev@gmail.com> wrote:

> Hi!
>
> Looking into some issue, I've discovered that, to my surprise,
> Exceptions are serializable. Except that it doesn't always work of
> course (e.g. see http://stackoverflow.com/q/9747813/214196) because
> exceptions contain backtraces, and those can contain non-serializable
> objects. So in reality, you never know if you can serialize it or not.
>
> So, I wonder - would it be ok to make exceptions not serializable at
> all? I think that would prevent major WTF factor when people try it and
> it randomly fails.
>
> Thoughts?
> --
> Stas Malyshev
> smalyshev@gmail.com
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--bcaec511e116b1d32e0511edfa7d--