Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87344
Return-Path: <rowan.collins@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 14550 invoked from network); 28 Jul 2015 15:50:33 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 28 Jul 2015 15:50:33 -0000
Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.171 as permitted sender)
X-PHP-List-Original-Sender: rowan.collins@gmail.com
X-Host-Fingerprint: 209.85.212.171 mail-wi0-f171.google.com  
Received: from [209.85.212.171] ([209.85.212.171:32846] helo=mail-wi0-f171.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 70/32-01209-8C4A7B55 for <internals@lists.php.net>; Tue, 28 Jul 2015 11:50:33 -0400
Received: by wicmv11 with SMTP id mv11so185282229wic.0
        for <internals@lists.php.net>; Tue, 28 Jul 2015 08:50:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=subject:to:references:from:message-id:date:user-agent:mime-version
         :in-reply-to:content-type:content-transfer-encoding;
        bh=hgPBAiBVrdZcXB/rMSwWa7iJz5scrVFA40sld3m2yxM=;
        b=VwfLaVs/fcOQzRIHd9YoNRb0KI4Ldxmg6IeurZFP5NreSF+69BWDBqyvtFdcxPVXXa
         vItVgTrAl/MQSf1YGrk84xSYqSaiZqL00CVpmfS3ircqGOAfvgXKuWrkSsBZjLPSYF93
         sI5C/r24KSHI1gPkAzoSmQuFzu399C7niNso50Lxxuvk/5Rt6+S0j9iXmqGuVqGJXCsr
         1HBIQkVdaCRFlv77m8mrccajGPLRkR3RtsR/eVL6m2ZbVMF2oL9mJOsPnLuB+lboomDk
         8icew7RKKsHd0tGfiPnP3FJ8aqID4srMjdT8uVg7xyMBiRs4tJofqFY1QgEjNCoQX8Ms
         SdQg==
X-Received: by 10.180.96.230 with SMTP id dv6mr8113401wib.23.1438098630465;
        Tue, 28 Jul 2015 08:50:30 -0700 (PDT)
Received: from [192.168.0.136] ([62.189.198.114])
        by smtp.googlemail.com with ESMTPSA id c7sm33896628wjb.19.2015.07.28.08.50.29
        for <internals@lists.php.net>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 28 Jul 2015 08:50:29 -0700 (PDT)
To: internals@lists.php.net
References: <550FA2ED.6080000@gmail.com>
 <CADR=R-gtCy7Vi7Y15jx+SYWX3aEB6TN3WGJPAqqQ4tO__SWqQw@mail.gmail.com>
 <CAF+90c8c8_Vth3vVaYF1N1u68JANTbGDq-QUTvG44X+Wr+oe0A@mail.gmail.com>
Message-ID: <55B7A4AC.9090401@gmail.com>
Date: Tue, 28 Jul 2015 16:50:04 +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: <CAF+90c8c8_Vth3vVaYF1N1u68JANTbGDq-QUTvG44X+Wr+oe0A@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)

Nikita Popov wrote on 28/07/2015 14:07:
> -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.
>
> Also, Christian Stoller's mail pointed out that Symfony uses serialized
> exceptions.

The problem is that exceptions *unpredictably* contain non-serializable 
members, because it depends on what's happened at arbitrary points in 
the backtrace. There is nothing a user catching an exception can do to 
predict or prevent it happening, unless (as I have repeatedly suggested) 
there is some way to strip the 'args' from the backtrace items.