Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87349 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34043 invoked from network); 28 Jul 2015 20:34:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jul 2015 20:34:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=ocramius@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ocramius@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.170 as permitted sender) X-PHP-List-Original-Sender: ocramius@gmail.com X-Host-Fingerprint: 209.85.212.170 mail-wi0-f170.google.com Received: from [209.85.212.170] ([209.85.212.170:35913] helo=mail-wi0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/B1-22108-347E7B55 for ; Tue, 28 Jul 2015 16:34:11 -0400 Received: by wicgb10 with SMTP id gb10so172681857wic.1 for ; Tue, 28 Jul 2015 13:34:08 -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=CnHRHhbi9xGmmF7PEp5jsRmYYNgvukc93HIOHmqRYjc=; b=L+1QhFnERzBzNvBzaBmMogtB2OP2IRGbpHcYG0oP4FQMIjizu5E54c0pKpOEmE0ueL MoPZi26OT+upZpHGEn/ojQ3A+TG1HokmGxN0pgHcy3SvNJPqKjTky07uPWOQKrw2gcsa RHYVz4L9iFsOhnZFLas0+88M2IVwJwV+jNatuEtrIxJgpnu/Bu5jcIft0z8G+9f6E2oT T5sfW1z9Dz80UuXHWyC5T90zS3FLpw2+XVlR/YQ0yfqjXOUI/uJV8wRWTWyLurUSI26B RX4x5CHG/1I2E35qNQ1B6caFPo9zImYJSmhOnsqATFIJqJXT8DwcdYXpc8WpKlIMBrtq cW1A== MIME-Version: 1.0 X-Received: by 10.180.78.35 with SMTP id y3mr37819090wiw.62.1438115648549; Tue, 28 Jul 2015 13:34:08 -0700 (PDT) Received: by 10.28.49.133 with HTTP; Tue, 28 Jul 2015 13:34:06 -0700 (PDT) Received: by 10.28.49.133 with HTTP; Tue, 28 Jul 2015 13:34:06 -0700 (PDT) In-Reply-To: <55B7B08E.7070700@gmail.com> References: <550FA2ED.6080000@gmail.com> <55B7B08E.7070700@gmail.com> Date: Tue, 28 Jul 2015 23:34:06 +0300 Message-ID: To: Stanislav Malyshev Cc: Nikita Popov , PHP Internals List Content-Type: multipart/alternative; boundary=f46d043c7b8460ba66051bf56411 Subject: Re: [PHP-DEV] Re: Serializing exceptions From: ocramius@gmail.com (Marco Pivetta) --f46d043c7b8460ba66051bf56411 Content-Type: text/plain; charset=UTF-8 This sort of change would be a major BC break for 8.x or similar. I also don't see security implications, tbh. On Jul 28, 2015 18:41, "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, 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 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --f46d043c7b8460ba66051bf56411--