Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85058 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35193 invoked from network); 16 Mar 2015 14:23:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Mar 2015 14:23:39 -0000 Authentication-Results: pb1.pair.com header.from=kris@koehntopp.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=kris@koehntopp.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain koehntopp.de from 85.214.51.51 cause and error) X-PHP-List-Original-Sender: kris@koehntopp.de X-Host-Fingerprint: 85.214.51.51 newroot.koehntopp.de Received: from [85.214.51.51] ([85.214.51.51:46357] helo=koehntopp.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 38/00-34940-967E6055 for ; Mon, 16 Mar 2015 09:23:38 -0500 Received: from brln-4d0c1f57.pool.mediaways.net ([77.12.31.87] helo=kk.home.koehntopp.de) by koehntopp.de with esmtpsa (Cipher TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.83 #3 (Debian)) id 1YXVva-0002x6-70; Mon, 16 Mar 2015 15:23:34 +0100 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_9B2710D3-3596-4BB0-889A-7266E879E2BF"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b5 In-Reply-To: <7AFD41A7-2612-40CC-A0E2-2A95034F7A5B@koehntopp.de> Date: Mon, 16 Mar 2015 15:23:28 +0100 Cc: "internals@lists.php.net" Message-ID: <8CF37FE9-ECC3-425D-ACD0-6750935F888E@koehntopp.de> References: <7AFD41A7-2612-40CC-A0E2-2A95034F7A5B@koehntopp.de> To: Anthony Ferrara X-Mailer: Apple Mail (2.2070.6) Subject: Re: [PHP-DEV] Voting irregularities From: kris@koehntopp.de (=?utf-8?Q?Kristian_K=C3=B6hntopp?=) --Apple-Mail=_9B2710D3-3596-4BB0-889A-7266E879E2BF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On 16.03.2015, at 15:03, Kristian K=C3=B6hntopp = wrote: >=20 > That is me. And I voted no on a broken poposal. And because some people asked, the kk account is not new. I have been using PHP since about 1997/98, joining the community around = the times of the first PHP 3.0 beta-releases. Boris Erdmann and I wrote = something called PHPLIB = (http://marc.info/?l=3Dphp-general&m=3D90222503034131&w=3D2, = http://marc.info/?l=3Dphp-general&m=3D90281652210710&w=3D2) = which implemented some kind of session management that has been = rewritten into the session module of PHP 4. I also wrote the Posix and Recode extensions back then, worked on the = LDAP extension, and dissed Zeev because of the C++ way of implementing = constructors instead of using __init or __construct = (http://www.mail-archive.com/php-dev@lists.php.net/msg36275.html, and = many other messages before that). I also annoyed people into = implementing __get, __set and __call, which over time became = http://php.net/manual/en/language.oop5.magic.php I blogged = https://plus.google.com/u/0/+KristianK%C3%B6hntopp/posts/ijoDNH2M8mB, = and apparently that motivated a number of people to look into this and = form an opinion, which is good. PHP already has too many things that can = be enabled and disabled at the language level, and too many ways to = enable and disable functionality in the language. It should have one = typing system, not many and certainly not any way to switch these on and = off, no matter how. At the current state and climate of discussion I personally think it = would be best for the language and the community for each and every = proposal to change the type system to fail or be withdrawn. =46rom my current experience, it may have been best for the language to = have chosen the Python way of things back 20 years ago >>> 3 + "2" Traceback (most recent call last): File "", line 1, in TypeError: unsupported operand type(s) for +: 'int' and 'str' >>> 3 + int("2") 5 >>> 3 + int("2a") Traceback (most recent call last): File "", line 1, in ValueError: invalid literal for int() with base 10: '2a' but it is too late now. Neither of the current proposals actually = improves a lot for anybody, but making that improvement optional, how = little it may ever be, is just insane. If you MUST have one proposal succeeding, I am of the opinion that one = should support the one by Zeev with the modification that it actually = warns about things instead of erroring right now (E_DEPRECATED or = something), and make that errors in the release after the current. I do = think that because it is ONE type system, not optional and because it = actually finds things that are broken and complains about these. Just = make the transition more gradual than it is now, in order to ease = adoption. K -- Kristian K=C3=B6hntopp http://google.com/+KristianKohntopp --Apple-Mail=_9B2710D3-3596-4BB0-889A-7266E879E2BF Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVBudgAAoJEIvpHAq9EUv1PMoP/jCmWp33ssEWySHnOljCno5A Ll8Jnn4SEM4NjCaurRfeOX1U7h+2uq3CHVhCOzdn46wi6umvZofIquax4TCG8vWV MPaEhjguToXW9VsSJaTz2bAOBDi9WtUKrouy5eb4zw19xfqP2G6ru28Fjj9UhQVJ tufhpLSPd5MtdiLUQzP341JPlUSnRPCw55t0y+P0q32UdAskd7HFQ28U/RjcGCRZ pWZRnyF+sCTLIkfbWe30I+qSylmCfahkR5npaubnxawrFN+lJCjpTmd8t6ZVc0br IRCkTOVpS37PgqkIIKyikPBspmDnqutqIr7yR77TxUweW1k94EKKSXo6kXa90+ex xPnVPzyRew+KEfWyt7GA52xzQvCGnJiPuj3lNX/39YWmKPiylVy/oG9vhuZ521Qh 75M33YjhaZZJ3ImL9IYuXJrnSHGRVR+7c+kU0iU8gc9TeUCYat2bx5ymCkSpOORX iDhqDLrryH1hz0Y/Mvy4imivWnxhf4GY/aaz1CMmyI4J0amOzpEevaM+6Aj0ZDQI zB2YVl83BO30B5Jq5ek77VcJMTYvvSmor4eLPO2mpttE/Dg4y55GTZKf1uUOtD3S gQBdBndjBDDp5bkj9zjnx31PcPJPYxVNeE+zFlLo8ReVvaYVgp4CXm5rY8cCtx0o +A7S1p+DuIwwLZ/DaGmN =zwfM -----END PGP SIGNATURE----- --Apple-Mail=_9B2710D3-3596-4BB0-889A-7266E879E2BF--