Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85419 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50108 invoked from network); 23 Mar 2015 06:11:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Mar 2015 06:11:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@tutteli.ch; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=php@tutteli.ch; sender-id=pass Received-SPF: pass (pb1.pair.com: domain tutteli.ch designates 80.74.154.78 as permitted sender) X-PHP-List-Original-Sender: php@tutteli.ch X-Host-Fingerprint: 80.74.154.78 ns73.kreativmedia.ch Linux 2.6 Received: from [80.74.154.78] ([80.74.154.78:41192] helo=hyperion.kreativmedia.ch) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4A/11-44294-7AEAF055 for ; Mon, 23 Mar 2015 01:11:53 -0500 Received: (qmail 5629 invoked from network); 23 Mar 2015 07:11:48 +0100 Received: from cm135-167.liwest.at (HELO RoLaptop) (81.10.135.167) by ns73.kreativmedia.ch with ESMTPSA (AES256-SHA encrypted, authenticated); 23 Mar 2015 07:11:48 +0100 To: "'Pierre Joye'" , "'Juan Basso'" Cc: "'Stanislav Malyshev'" , "'PHP Internals'" References: <550FA2ED.6080000@gmail.com> In-Reply-To: Date: Mon, 23 Mar 2015 07:11:46 +0100 Message-ID: <000901d06530$3f0a9c80$bd1fd580$@tutteli.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQGkqh/2VO9aX+2MxEE5sWEw0iYXWwHeaC2zAgYtniudYedCIA== Content-Language: de-ch Subject: AW: [PHP-DEV] Serializing exceptions From: php@tutteli.ch ("Robert Stoll") > -----Urspr=C3=BCngliche Nachricht----- > Von: Pierre Joye [mailto:pierre.php@gmail.com] > Gesendet: Montag, 23. M=C3=A4rz 2015 06:57 > An: Juan Basso > Cc: Stanislav Malyshev; PHP Internals > Betreff: Re: [PHP-DEV] Serializing exceptions >=20 > On Mon, Mar 23, 2015 at 12:31 PM, Juan Basso = wrote: > > Maybe you can implement the __sleep method and just return the > > documented attributes (message, code, file, line). > > > > Not perfect, but probably more useful than throw an exception, > > specially if the exception is something that is the attribute of = some > > object that is being serialized. >=20 > Well, can someone explain me why some code would need to serialize = exception in the 1st place? >=20 > Cheers, > -- > Pierre >=20 > @pierrejoye | http://www.libgd.org >=20 > -- > PHP Internals - PHP Runtime Development Mailing List To unsubscribe, = visit: http://www.php.net/unsub.php Maybe some user defined mechanism for remote exception handling