Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87450 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 88198 invoked from network); 31 Jul 2015 19:21:27 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Jul 2015 19:21:27 -0000 Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.49 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.215.49 mail-la0-f49.google.com Received: from [209.85.215.49] ([209.85.215.49:34786] helo=mail-la0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9F/47-47755-4BACBB55 for ; Fri, 31 Jul 2015 15:21:25 -0400 Received: by lafd3 with SMTP id d3so50178855laf.1 for ; Fri, 31 Jul 2015 12:21:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AWN7NqqUmzGY7p+aH913Cen7j0BnDX1pTS6VtHvHpW0=; b=JNvyFSEF47y8afGpaoxVia91h10njdoXSht1uGoFbI4Nu9TP4OeVNhgO3TSs6sfw6W IsIDgadfBHB8wTcExsNeXM5ZGDcoI3iZEpVX0/lXLKPTtsj93d1t9fpDeA2sSGKlZ9iT aEVoCPwpY85S2wq1vLu7rkYxFCmv/mzNUHbH7bva1AaSjCT58TFs5UIhVrWgqSsljcmv owSFYp+GAvVMF5JYy5YhKL8FdaMeEh6NC4zCa8F2NUXKTY9pigGfdHozl/Iwj5PHQ7B+ NSxoxFVUdrx8pCr77VYByMbCmFaqUIWtMpCP/MZATRES6N4aKT+cckvRfEBStlf4VeBN zbKg== MIME-Version: 1.0 X-Received: by 10.112.210.6 with SMTP id mq6mr4809202lbc.83.1438370481822; Fri, 31 Jul 2015 12:21:21 -0700 (PDT) Received: by 10.152.43.105 with HTTP; Fri, 31 Jul 2015 12:21:21 -0700 (PDT) In-Reply-To: <55B7B08E.7070700@gmail.com> References: <550FA2ED.6080000@gmail.com> <55B7B08E.7070700@gmail.com> Date: Fri, 31 Jul 2015 21:21:21 +0200 Message-ID: To: Stanislav Malyshev Cc: Nikita Popov , PHP Internals Content-Type: multipart/alternative; boundary=001a11c3cc6e9fe317051c30b99a Subject: Re: [PHP-DEV] Re: Serializing exceptions From: tyra3l@gmail.com (Ferenc Kovacs) --001a11c3cc6e9fe317051c30b99a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jul 28, 2015 at 6:40 PM, Stanislav Malyshev wrote: > 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, thi= s > > 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. > > Personally I feel the restoring them impossible argument weak, consider that we allow stuff like serializing resources without even a notice. Based on my own experiences where I had to fix multiple apps when we introduced the unserializable Closure (mostly error logger and debugging tools) which got passed as argument in the backtrace I would prefer if we could remove that restriction. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu --001a11c3cc6e9fe317051c30b99a--