Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92006 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72883 invoked from network); 30 Mar 2016 05:13:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Mar 2016 05:13:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.161.179 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.161.179 mail-yw0-f179.google.com Received: from [209.85.161.179] ([209.85.161.179:33408] helo=mail-yw0-f179.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F9/0E-24137-9806BF65 for ; Wed, 30 Mar 2016 00:13:46 -0500 Received: by mail-yw0-f179.google.com with SMTP id h65so45333551ywe.0 for ; Tue, 29 Mar 2016 22:13:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pthreads-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=5/2dGTVCefT7QaJaMs3FCTCEmr81L0kD9mM2a8KZL5Y=; b=ahlXV4uDLC7ZvnIxHXxcfi+tI5g81m7/oqA9yYsq42VGbxYdDmaIfqq5FH3HgLrFLP y2ULDZ/VS9zN5r1rq9Jy+uf8LAq58SG0KpeLBeZKtiIFwf3I8WCIldoLT3UNsGXgXrzw V5PJTj39zZ8deauRvE0Au2kn0pZlAHbnKBtd33UsMqrkW4VzSWyN0r6iLzk47EOb7+oK g+N3CuXXJE0WZ0tcFkIS1Wbs65EwjHdpzzktocGrkyFjc2hclQl+B9bs5eS418dKZ+L6 1gxVK2hczcEvKw+s0l2leKZrpT026cJ2by0W81JZEmfzOH7zEaFjaFRQXDwstaMDuTU8 fliQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=5/2dGTVCefT7QaJaMs3FCTCEmr81L0kD9mM2a8KZL5Y=; b=F0zD0CJH+JhWJtQRJ+I7Qe06hUfRZ4/zcVlx0qBRAdXQisXKi36496Dy1OSsp4H9tE lWtojfK4rjP1CCuzGaG/NemGjvh2LR1QR0ipR+NYqATi4lKUZ2ja+0pWonZk1Z+Ht3AZ 4f/VKpCWRFcCIqc0RnE/Rj/Cc7p54BRPyY0hLf7ox2SQSvtkSRIugUHu6/AlsK+p5xDE f9cHt+JgxzqfMjn+mjwR2rGlHk2uK7IUOjLnYyDVtGn4URPLc/KPkSRnw1EGuW5u1h3f zXJQVZsGtYW39ehtRc/LVFBM7xsDYcfb4GLTOPZdGmWSG+yB0cC9LSDl+paz7tIIni0U Vwlw== X-Gm-Message-State: AD7BkJJYtBo47iDOVK1pSMZxxS2uLItixz9qsERXTeId0ozJFcnFkONLvVcudVGW7x0xScYV9o58PlguWiGJeA== MIME-Version: 1.0 X-Received: by 10.37.4.142 with SMTP id 136mr3039706ybe.81.1459314822429; Tue, 29 Mar 2016 22:13:42 -0700 (PDT) Received: by 10.129.39.9 with HTTP; Tue, 29 Mar 2016 22:13:42 -0700 (PDT) X-Originating-IP: [109.159.6.57] In-Reply-To: References: <1458149992.3969.2.camel@kuechenschabe> <1458151531.3969.8.camel@kuechenschabe> <1458153695.3969.16.camel@kuechenschabe> <3F.70.02405.6803BE65@pb1.pair.com> <56F01545.8080008@gmail.com> <56F14572.701@gmail.com> <56F15EF5.80006@telia.com> <56F16023.1010002@gmail.com> Date: Wed, 30 Mar 2016 06:13:42 +0100 Message-ID: To: Pierre Joye Cc: PHP internals , Philip Sturgeon , "krakjoe@php.net" , Dmitry Stogov Content-Type: multipart/alternative; boundary=001a11c009c29b75cb052f3d354a Subject: Re: [PHP-DEV] [RFC Discussion] Typed Properties From: pthreads@pthreads.org (Joe Watkins) --001a11c009c29b75cb052f3d354a Content-Type: text/plain; charset=UTF-8 Morning Dmitry, So, I quickly reviewed the RFC and patch. Static properties, and mixed declarations, are now explained in the RFC. I made a couple of changes to the fetch_obj_w stuff, I'd be grateful if you could review that ... I didn't think I had got all possible combinations, should be bit better, and drier ... The overflow related stuff, I'll fix and explain in the RFC, but I'll let you have a go at perf stuff, and other outstanding things now ... */me leaves patch alone* Cheers Joe On Wed, Mar 30, 2016 at 5:26 AM, Joe Watkins wrote: > Morning Pieere, Dmitry, all ... > > Actually it's not so simple ... for object properties we have ASSIGN_OBJ > opcode, but we don't have a special opcode for static properties, and > ASSIGN doesn't have any information about where the var came from, and nor > should it have that information ... > > I'm going to stick the original decision, static properties don't belong > until typed variables are a thing ... > > Cheers > Joe > > On Wed, Mar 30, 2016 at 4:57 AM, Pierre Joye wrote: > >> >> On Mar 30, 2016 10:17 AM, "Joe Watkins" wrote: >> > >> > Morning Dmitry, >> > >> > > 1) static typed properties are prohibited. why? >> > >> > Feels like that's a separate feature, static properties are as good as >> > makes no difference, global variables. >> > >> > Instance properties, the engine has good control over their >> manipulation, >> > for static properties it doesn't, it's not impossible, but feels >> separate. >> >> Internally different but from users perspective it is the same (a class >> property). It would be nice to support that at the same time to avoid >> confusion. >> > > --001a11c009c29b75cb052f3d354a--