Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:87352 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 39271 invoked from network); 28 Jul 2015 20:46:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jul 2015 20:46:31 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.176 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.176 mail-pd0-f176.google.com Received: from [209.85.192.176] ([209.85.192.176:34688] helo=mail-pd0-f176.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0B/D2-22108-72AE7B55 for ; Tue, 28 Jul 2015 16:46:31 -0400 Received: by pdbbh15 with SMTP id bh15so76449327pdb.1 for ; Tue, 28 Jul 2015 13:46:28 -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=M/RqjlXBRS+uDHkDEybluifbOhUxFXSLZ+DQo5h/DFM=; b=LraxQJ6e29csDwnnQopcOvIK9NPpc/5Od4+qEdFBgENYnrxEn7pKnvEAyGarLfX5nw Cow33fsNg3JKJzAjk6UGV4PvwR+u33sf6+JdT5HoXR2ZOGS1xcT5YklP/ablGb1Kk7xP qo4IQ5N/GpYMR6UGow9bguDAKoBa13sUyoCk7HQZJsrA10QD2ua2pJvAqHWHoSsUlj1I lcW7tWVDjGu60y0h3Thbw7LAQAWFjxuAt8lpOlxA/+pxh0ieZqSh7J6mmJjF+4MkXC9Y 15CoApdiGYkLzHB93hEDShFJ+p9dR+cqAXBF+eFQK9lYI9k/PCMfGlwAs9g+btp/8AA1 vHxg== X-Received: by 10.70.103.37 with SMTP id ft5mr8057971pdb.83.1438116388130; Tue, 28 Jul 2015 13:46:28 -0700 (PDT) Received: from Stas-Air.local ([166.177.251.175]) by smtp.gmail.com with ESMTPSA id pe3sm36765052pdb.55.2015.07.28.13.46.26 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jul 2015 13:46:27 -0700 (PDT) To: Marco Pivetta References: <550FA2ED.6080000@gmail.com> <55B7B08E.7070700@gmail.com> Cc: Nikita Popov , PHP Internals List X-Enigmail-Draft-Status: N1110 Message-ID: <55B7EA22.7060504@gmail.com> Date: Tue, 28 Jul 2015 13:46:26 -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: 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! > This sort of change would be a major BC break for 8.x or similar. How is it a major BC break? You make it sound like serializing exceptions is something no application can do without. I have yet to see a single case where it's useful (yes, I've read the Symphony comment but I'm not sure why they're doing it and if it's indeed something that should be done and not an ugly hack like unserializing fake internal objects). > I also don't see security implications, tbh. I don't want to discuss it in detail yet, but check out currently open or recently fixed security issues and see how many of them relate to serialized exceptions and consequences of that. -- Stas Malyshev smalyshev@gmail.com