Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:92005 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69079 invoked from network); 30 Mar 2016 04:26:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Mar 2016 04:26:45 -0000 Authentication-Results: pb1.pair.com header.from=pthreads@pthreads.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=pthreads@pthreads.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pthreads.org from 209.85.161.177 cause and error) X-PHP-List-Original-Sender: pthreads@pthreads.org X-Host-Fingerprint: 209.85.161.177 mail-yw0-f177.google.com Received: from [209.85.161.177] ([209.85.161.177:35331] helo=mail-yw0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E4/AD-24137-4855BF65 for ; Tue, 29 Mar 2016 23:26:45 -0500 Received: by mail-yw0-f177.google.com with SMTP id g127so44318462ywf.2 for ; Tue, 29 Mar 2016 21:26:44 -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=VZWKn7LUHf6pt4wye/hmszuWh4MaU5SnbgD37HLvK6E=; b=aE2O9//0mW1pG1Q5U5dz0DSDSChP/EcG2oaKo6LdjIxbjGoOef7PXR4ydrkTNUz1BQ YHwgILfzGv88SqB5lYbAc8yqXiRo9tgAjmedBGs5nMGJCZE2pgI2sCN9JVxftj4TG3HB ISmu1d4dmHM+8MLKOScbDMLdoaq5F1Djh2ePppqObojQ2aBJmAafWuQAW2FY/VNXcNBd mgoIS1bD+MFAG1HDoZo7KTMSSAjPvorJBad2DcrQgGU7YndzhW16JldtCYbHsX0AqOiw kI+EKIsFP4GR260BS6MTZhoUsYIE+6Mp3NpV9xxWfdqXg4TwcC2cbJgIUnlPwrsMg6B6 8COw== 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=VZWKn7LUHf6pt4wye/hmszuWh4MaU5SnbgD37HLvK6E=; b=WYoCgEJ5y7ktJVYzGwxU5MPaW7nsBSgM4GJV7OrARaLYndqXOQQ1hCa3/C0PmQdVW3 QI50zpjAt0+mX0RGWZUqgyHtJVv669YuXnfNhR7ilyxFZmCHoOYqoDPeeBcmfTIS2X5+ 1b0xoPs4IN0wUmZI/VlTNOXjPuqcGRFTv/V1chVYYEx46YFuBEy32e7RlO8gnQokPmsF eQoKLblnqMbYIStCWRKKlLOWZ6uoAOglkKr6njIJu8XRyC4JY8L31pPG0jaxxfnB6op9 xIHf2q+6SQXmsUS4B77B4NAo+8moqUWQrSIHHeWe3xJxjEaA+j4UQVuBDuE2GJimC9pP QIzg== X-Gm-Message-State: AD7BkJKep/QsMgyBAJ9GwhkFO5w51Am+VA69i0BW/ns1CX3EmoPyCvM5n4ccClIpyowWh897JA43NSJPHuworg== MIME-Version: 1.0 X-Received: by 10.129.42.85 with SMTP id q82mr3418432ywq.265.1459312001473; Tue, 29 Mar 2016 21:26:41 -0700 (PDT) Received: by 10.129.39.9 with HTTP; Tue, 29 Mar 2016 21:26:41 -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 05:26:41 +0100 Message-ID: To: Pierre Joye Cc: PHP internals , Philip Sturgeon , "krakjoe@php.net" , Dmitry Stogov Content-Type: multipart/alternative; boundary=001a11422952772a8e052f3c8d67 Subject: Re: [PHP-DEV] [RFC Discussion] Typed Properties From: pthreads@pthreads.org (Joe Watkins) --001a11422952772a8e052f3c8d67 Content-Type: text/plain; charset=UTF-8 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. > --001a11422952772a8e052f3c8d67--