Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101576 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46093 invoked from network); 10 Jan 2018 14:10:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jan 2018 14:10:03 -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.52 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 74.125.82.52 mail-wm0-f52.google.com Received: from [74.125.82.52] ([74.125.82.52:39674] helo=mail-wm0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F3/B0-39025-ABE165A5 for ; Wed, 10 Jan 2018 09:10:03 -0500 Received: by mail-wm0-f52.google.com with SMTP id i11so27247798wmf.4 for ; Wed, 10 Jan 2018 06:10:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:from:message-id; bh=NXyD4RSxGaYpNOlD210ZcYu7Rd65Ta72qqem0Ebooc8=; b=IwmZs4is4guVnWR/2MIOzGSRxVtfzcaqTX+H0nUoGiCXyaN8h1nrSfKvBfoFxRCZf2 +C2eV+J3+sxSnLOPOl9i8M+xOvYJoKxUad4w3jGEUoozA6n2cGa2H+iB87GjXM4PUZtJ 0iDTpIFGjgIJkC3wpCB6p0KeWnixCHQ7SBYV9ZAsckFeZyK0L5b+WTic4k+LqxxG5Nk1 MaBjcZmzbHViqAohh/r7E1VMN2mOzHR0ZSvLg5w9c8qR/D7CLnKHrS54r0ZMfdidoN8P RGujMyOUE7IwAsPm6CIbe3BpaTTj/AgWipBxyOjkUNQ2Yz7bidRctQ1h1OSDISCMU/5S tSRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:from:message-id; bh=NXyD4RSxGaYpNOlD210ZcYu7Rd65Ta72qqem0Ebooc8=; b=umfBT72yP7POumD1cfh/CUteI9qe4P49B+8tpXMthK+XPfPadStZN6shEXxVDiXJTU 5Txkeuwbc5XsbbWREi/fZTOXnE1iSFS/C6YajcJ7wQyIgKlkjE7wu+DqIFNxQ1K/5Ev8 vg6bDOXrAfEKCYqI17b/r+1EJaWbTw/7hwODy7v31iVP7TgNnRNsE8jdPNP+UkB2lBzP VJ4H1JV3CmNV3UnSi9JgvyKrMfrX574ydrhdyopQ81r9vxCgXolnWRkUrbs5IyetdVfq Nq6hURJNimSRw8helT7oZiK3Ewzxg2yU1Xp4HEs6iPYXZ4nwvtxkF6zqtIIDYswcCvw/ L29w== X-Gm-Message-State: AKGB3mJjmLWmOgKlG+SWxTm/XSUOyiKxyaRU7wJxm316mwgllXyoGQES a6yrXggOfMzd8sFV3HmQCTT6wQ== X-Google-Smtp-Source: ACJfBouhEZsQdjgFy7GEr8KObXfAZjZuCLqfwqErpalBTZGPv9QwdiMrHRceuJccPAAEIHWzU3NGAA== X-Received: by 10.28.235.15 with SMTP id j15mr15680658wmh.52.1515593399496; Wed, 10 Jan 2018 06:09:59 -0800 (PST) Received: from [192.168.77.133] ([62.6.147.196]) by smtp.gmail.com with ESMTPSA id p17sm18942868wma.23.2018.01.10.06.09.58 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 10 Jan 2018 06:09:58 -0800 (PST) Date: Wed, 10 Jan 2018 14:09:57 +0000 User-Agent: K-9 Mail for Android In-Reply-To: References: <9a3a8760-f65a-a5c0-b318-1830a9a986c3@gmail.com> <9352F6DF-9940-49A2-9B1D-FA9258E9738E@lerdorf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: PHP internals Message-ID: <81E12AD5-2B5F-436E-BDE1-BD06BACEFC3F@gmail.com> Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Strong Typing Syntax From: rowan.collins@gmail.com (Rowan Collins) On 9 January 2018 23:06:54 GMT+00:00, Michael Morris = wrote: >Before I begin, and without picking on anyone specific, I want to say tha= t >it is generally unhelpful to say that because I, or others, do not know h= ow >the engine is set up that it is impossible to make any meaningful >contributions to the list or on this issue specifically=2E My clients do= n't >understand HTML=2E If I told them they needed to study how HTML works >before trying to give me input on the sites I'm building for them I'd lik= ely be fired=2E=20 While I understand your frustration, I don't think anyone here is saying y= ou shouldn't offer any input, only to be aware of your own limitations when= presenting it=2E To use your analogy, imagine if a client came to you and said "we think it= would be cool if the page changed colour as the user looked at different p= arts of the screen"=2E You probably wouldn't ask them for details of what c= olours they wanted, with a vague idea that you'd research if it was possibl= e to implement eye-tracking in browser JS later; more likely, you'd say "ye= s, that would be cool, but I'm pretty sure it's not possible"=2E If they we= nt ahead and gave you a 10-page spec "in case you work out how to do it aft= er all", that would be a waste of everyone's time=2E So, back to the subject at hand: it is useful to share ideas on the typing= strategy PHP should be taking, things like which types of value you'd like= to see checked, whether we need both auto-casting and type errors, whether= all of this should be switched off in production, and the implications for= the user of those various decisions=2E But there's always the possibility = that those ideals won't be possible, so details like the exact keywords to = use for each type of variable are probably best left vague and sorted out l= ater=2E I'll also echo a previous request that you apply for a wiki account to mak= e your document more readable; or maybe just put it as a github gist or on = your own website, and treat it as more of a wishlist and discussion piece t= han a spec that core developers are going to commit to=2E Regards, --=20 Rowan Collins [IMSoP]