Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87345
Return-Path: <smalyshev@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 18499 invoked from network); 28 Jul 2015 16:40:54 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 28 Jul 2015 16:40:54 -0000
Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.46 as permitted sender)
X-PHP-List-Original-Sender: smalyshev@gmail.com
X-Host-Fingerprint: 209.85.220.46 mail-pa0-f46.google.com  
Received: from [209.85.220.46] ([209.85.220.46:36297] helo=mail-pa0-f46.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 11/C2-01209-590B7B55 for <internals@lists.php.net>; Tue, 28 Jul 2015 12:40:54 -0400
Received: by pachj5 with SMTP id hj5so72362123pac.3
        for <internals@lists.php.net>; Tue, 28 Jul 2015 09:40:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=subject:to:references:cc:from:message-id:date:user-agent
         :mime-version:in-reply-to:content-type:content-transfer-encoding;
        bh=aoHITBoOp0MtvaFgwFO5bG4qQTmeETnCV5uU2Ky6VsU=;
        b=Yyol22nWiEWto5WfdvmPfhK28sUleERh1LMecDROofeMDztklCSFIQYUYO1Qi+UvDa
         IuSkgiXCqOgZm8I9f31sALoilW5Tyo6jwhQ2u3zZWuklOxzJcYqBUq4GQ/hH55for4Qn
         kZuoKkbeSNs+UtCl40BQHMcJ6saf61CcldOEM4QMrQMFet963IfU3vRYSCya9DWZBwM5
         5l6hYxCUPO+bgLlvGEmT35zbzhbPAy7j0yAmqPsgGNk4TZ0+KXzoKoSscACyco7Dhej0
         XDrPbE8Q2oEE4ophQz2nohkdNEIpzNffMjmT/IknfAptT29zqnYtT19b+fjhS5B216j1
         81Cw==
X-Received: by 10.66.66.40 with SMTP id c8mr84509522pat.117.1438101650917;
        Tue, 28 Jul 2015 09:40:50 -0700 (PDT)
Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48])
        by smtp.gmail.com with ESMTPSA id jw13sm33915485pad.48.2015.07.28.09.40.49
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 28 Jul 2015 09:40:50 -0700 (PDT)
To: Nikita Popov <nikita.ppv@gmail.com>
References: <550FA2ED.6080000@gmail.com>
 <CADR=R-gtCy7Vi7Y15jx+SYWX3aEB6TN3WGJPAqqQ4tO__SWqQw@mail.gmail.com>
 <CAF+90c8c8_Vth3vVaYF1N1u68JANTbGDq-QUTvG44X+Wr+oe0A@mail.gmail.com>
Cc: PHP Internals <internals@lists.php.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <55B7B08E.7070700@gmail.com>
Date: Tue, 28 Jul 2015 09:40:46 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <CAF+90c8c8_Vth3vVaYF1N1u68JANTbGDq-QUTvG44X+Wr+oe0A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Serializing exceptions
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> -1 on this. If there is no technical problem with serializing the
> Exception class itself, it should be possible to serialize it. It can
> always happen that an object contains some not-serializable member, this
> is nothing specific to exceptions. I don't see the point of this change.

The point is exactly that Exception contains non-serializable members
that makes successfully serializing and restoring them impossible. You
could get back something that looks like an Exception, but not the
original one - namely, you can not store and restore backtraces.

> Also, Christian Stoller's mail pointed out that Symfony uses serialized
> exceptions.

I must have missed it - what Symphony uses serialized exceptions for?

-- 
Stas Malyshev
smalyshev@gmail.com