Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69272 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41912 invoked from network); 23 Sep 2013 14:38:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Sep 2013 14:38:42 -0000 Authentication-Results: pb1.pair.com header.from=bof@bof.de; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=bof@bof.de; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain bof.de designates 80.242.145.70 as permitted sender) X-PHP-List-Original-Sender: bof@bof.de X-Host-Fingerprint: 80.242.145.70 mars.intermailgate.com Received: from [80.242.145.70] ([80.242.145.70:57528] helo=mars.intermailgate.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1D/00-41312-F6250425 for ; Mon, 23 Sep 2013 10:38:41 -0400 Received: (qmail 2840 invoked by uid 1009); 23 Sep 2013 16:38:36 +0200 Received: from 209.85.128.179 by mars (envelope-from , uid 89) with qmail-scanner-1.25-st-qms (clamdscan: 0.96.2/17886. spamassassin: 3.3.1. perlscan: 1.25-st-qms. Clear:RC:1(209.85.128.179):. Processed in 0.075853 secs); 23 Sep 2013 14:38:36 -0000 X-Antivirus-MYDOMAIN-Mail-From: bof@bof.de via mars X-Antivirus-MYDOMAIN: 1.25-st-qms (Clear:RC:1(209.85.128.179):. Processed in 0.075853 secs Process 2834) Received: from mail-ve0-f179.google.com (gmail@bof.de@209.85.128.179) by mars.intermailgate.com with RC4-SHA encrypted SMTP; 23 Sep 2013 16:38:36 +0200 Received: by mail-ve0-f179.google.com with SMTP id c14so2272102vea.24 for ; Mon, 23 Sep 2013 07:38:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3JdzCBbpcZDpTGWSLcpp0pN1jpTpD5dzRcqS7SoXhSs=; b=KAH5wyYwrGa038rByo4cma1NgphInv6r760t7wviUg9iFu2Xs0TbpyRvOWliE1FjVh w0E8AL19CML9k16JEWQOOArJCZBKHvgflyAM7SJWoJpEcTJG6li2fIjOhE0Bmj335bhd w/5ABJMJ2wrZCs4tNEsDkIShwbnn+un36ZKR/+QV5a0fclLOjpnVAqm4UVvJTKVA8AU4 HTfVxKxGrOJ51j3bpx6KooUz//P3VuRiL01eaOXxJIovurC97g6YDcdn9p9Zdk+1F55+ bZD6eiQFu4sJ061YEMd2SublIWVhybg34En0SMbABMFhxRgPBCt5tFzszOZJnyRrAitb fuTw== MIME-Version: 1.0 X-Received: by 10.58.169.193 with SMTP id ag1mr883938vec.26.1379947115114; Mon, 23 Sep 2013 07:38:35 -0700 (PDT) Received: by 10.52.24.43 with HTTP; Mon, 23 Sep 2013 07:38:34 -0700 (PDT) Received: by 10.52.24.43 with HTTP; Mon, 23 Sep 2013 07:38:34 -0700 (PDT) In-Reply-To: <52404AB9.2070007@php.net> References: <52404AB9.2070007@php.net> Date: Mon, 23 Sep 2013 16:38:34 +0200 Message-ID: To: Joe Watkins Cc: Lars Strojny , internals Content-Type: multipart/alternative; boundary=047d7b6d841c9b0f3f04e70df906 Subject: Re: [PHP-DEV] RFC: Anonymous Classes From: bof@bof.de (Patrick Schaaf) --047d7b6d841c9b0f3f04e70df906 Content-Type: text/plain; charset=ISO-8859-1 Am 23.09.2013 16:06 schrieb "Joe Watkins" : > > On 09/23/2013 02:43 PM, Lars Strojny wrote: >> >> what about serialization for those classes? > > Same as any other object; what you are creating is normal classes without a (declared) name, nothing about the objects functionality has differs from an object of a named class. What about UNserialize then? Will you extend the serialized format to include the full definition of the anonymous class, so that it can be reinstated at unserialization time? If not, what will be the class (and baseclass and interfaces) of the unserialized formerly-anonymous objects? best regards Patrick --047d7b6d841c9b0f3f04e70df906--