Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93353 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 97237 invoked from network); 16 May 2016 09:18:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 May 2016 09:18:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.49 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.49 mail-wm0-f49.google.com Received: from [74.125.82.49] ([74.125.82.49:35667] helo=mail-wm0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E3/A3-65275-46099375 for ; Mon, 16 May 2016 05:18:29 -0400 Received: by mail-wm0-f49.google.com with SMTP id e201so92976315wme.0 for ; Mon, 16 May 2016 02:18:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=gX23QSlekHKSvtFye/nhh4gc8thRSETSGFSnW2r47z4=; b=luaJz3gcYN1MqDduwsmJVjbjVq3MwdQTiZ/D2sIvgRPQZdCHVEjHbxwIhbDopNAlqB UZkhoXSni/iICnHl6CdkobYy88H2LCSlmyWm9shupe5w8YesCChgQp8V8vcQSKn0yJga ag7aloD/oRKKeOVBPIcPfj790U9fUPkGTQPYZ/Yul6FBUVLiXsKNuBGIAHiygyO5AL7V 837Uwjf1SpGRP8qDCMHg0S/gqRZ+LDOjnsiV1G4606XnCyubrwhWNAXUySjlQ8oRRPtM lu1Yd0m0m859B5Ayx2jVAf1avmVFDXC5hXzCfAsMZZyqf3CI0uDkunJoUJA9vO3+TSMJ lRBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=gX23QSlekHKSvtFye/nhh4gc8thRSETSGFSnW2r47z4=; b=A/d/o8stsfpwtLrWzWiF2LvaUBe5Hg3K7KzeaKixP+X8d+JXqk1avc6SK6Jwe8A8AG MvsyTdtm1e+S7k4VyO8qHlWU5Xrf3rT6m56o9xKAUgV8wWjaRjkEvSStWa8T2vwIQrZG dc8ep2vEyt8JlJUQJ21l3fDe3aO9huI7RhFHdUUQ0V2FiHZbgLYRlXA/9IbzR36ejev1 7C0s1Hf+kGq6zmEsqi4LdS0ZKykXi+ljTewCDr/w9PwBiOAY4cgLmDnZSF8vqoaS1sA1 3H1NYxQuVghhd2D9rjwXd1HC/0BGWIprpSrf5LMSazxDrOMXABEYQ4kEblyqVrllUx7S iMog== X-Gm-Message-State: AOPr4FWyGahk+lFYzn6KawrO9B1Rk72Og7AyY5TUqSeqhsEVOVZOXI1MaepkCouFH3S6Dg== X-Received: by 10.28.216.76 with SMTP id p73mr17496297wmg.3.1463390305538; Mon, 16 May 2016 02:18:25 -0700 (PDT) Received: from [192.168.0.98] ([93.188.182.58]) by smtp.gmail.com with ESMTPSA id ip10sm32595965wjb.33.2016.05.16.02.18.24 for (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2016 02:18:24 -0700 (PDT) To: internals@lists.php.net References: Message-ID: <61e6a083-91c2-799f-9757-02f56fe184e9@gmail.com> Date: Mon, 16 May 2016 10:16:34 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Simple Annotations From: rowan.collins@gmail.com (Rowan Collins) On 14/05/2016 20:49, Rasmus Schultz wrote: > Dan, > > I've added a note about special annotations to the "future scope" > section, naming the memoization-annotation as an example. This doesn't really explain how such a feature would fit it into the proposal. For instance, how can we avoid the syntax clashing with existing userland issues? Given that annotations in this proposal don't have names, we can't just reserve all names beginning "__" or "php\". Perhaps they would be pseudo-function calls, like <<__memoize()>>? How would that (or any other undefined function) act if accessed on a version that didn't have the feature? I realise you don't want to define the details, but an idea of what an annotation targeting the engine would look like would make the future-proofing clearer. Regards, -- Rowan Collins [IMSoP]