Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93600 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67478 invoked from network); 27 May 2016 08:52:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 May 2016 08:52:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@fleshgrinder.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=php@fleshgrinder.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fleshgrinder.com from 212.232.25.164 cause and error) X-PHP-List-Original-Sender: php@fleshgrinder.com X-Host-Fingerprint: 212.232.25.164 mx208.easyname.com Received: from [212.232.25.164] ([212.232.25.164:50525] helo=mx208.easyname.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 51/F4-37127-1DA08475 for ; Fri, 27 May 2016 04:52:34 -0400 Received: from cable-81-173-133-15.netcologne.de ([81.173.133.15] helo=[192.168.178.20]) by mx.easyname.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1b6DVO-0006cw-RV; Fri, 27 May 2016 08:52:31 +0000 Reply-To: internals@lists.php.net References: <20160525215208.034FC1A801B3@dd1730.kasserver.com> <5fd54aa0-4fdf-c1e7-eae8-765aa89c8498@fleshgrinder.com> <08963b03-8394-6d62-4e5b-393f3fcb5647@fleshgrinder.com> <9e9db70d-d72d-d93e-0c81-18c2aa228618@gmail.com> <409002d8-b5e3-5990-7358-246adc7e3cab@fleshgrinder.com> <57474A08.80807@lsces.co.uk> <6f7403b6-bf22-a12b-dfb2-43fe82983e7d@fleshgrinder.com> <57474F9C.6080104@lsces.co.uk> <1733cfce-001b-1079-e929-88f7dde0f2dd@gmail.com> <57475F27.3090306@lsces.co.uk> <50f5d1c9-d24f-1afe-4c34-70aafd981524@fleshgrinder.com> <5747697A.7000906@lsces.co.uk> <37377d3b-827a-4cfd-580b-e33862084ab6@gmail.com> <5747F02A.2010808@lsces.co.uk> To: Tony Marston , internals@lists.php.net Message-ID: <2049e48d-5dd3-051b-2564-afeb8c64ca48@fleshgrinder.com> Date: Fri, 27 May 2016 10:52:15 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ngOwas2EDd0tpdCpf9pfKQPlAIxGS2UQI" X-ACL-Warn: X-DNSBL-BARRACUDACENTRAL Subject: Re: [PHP-DEV] [RFC][Vote] Typed Properties From: php@fleshgrinder.com (Fleshgrinder) --ngOwas2EDd0tpdCpf9pfKQPlAIxGS2UQI Content-Type: multipart/mixed; boundary="11TdTubKw3mMChWUoFT6qvihHbe1CmR8i" From: Fleshgrinder Reply-To: internals@lists.php.net To: Tony Marston , internals@lists.php.net Message-ID: <2049e48d-5dd3-051b-2564-afeb8c64ca48@fleshgrinder.com> Subject: Re: [PHP-DEV] [RFC][Vote] Typed Properties References: <20160525215208.034FC1A801B3@dd1730.kasserver.com> <5fd54aa0-4fdf-c1e7-eae8-765aa89c8498@fleshgrinder.com> <08963b03-8394-6d62-4e5b-393f3fcb5647@fleshgrinder.com> <9e9db70d-d72d-d93e-0c81-18c2aa228618@gmail.com> <409002d8-b5e3-5990-7358-246adc7e3cab@fleshgrinder.com> <57474A08.80807@lsces.co.uk> <6f7403b6-bf22-a12b-dfb2-43fe82983e7d@fleshgrinder.com> <57474F9C.6080104@lsces.co.uk> <1733cfce-001b-1079-e929-88f7dde0f2dd@gmail.com> <57475F27.3090306@lsces.co.uk> <50f5d1c9-d24f-1afe-4c34-70aafd981524@fleshgrinder.com> <5747697A.7000906@lsces.co.uk> <37377d3b-827a-4cfd-580b-e33862084ab6@gmail.com> <5747F02A.2010808@lsces.co.uk> In-Reply-To: --11TdTubKw3mMChWUoFT6qvihHbe1CmR8i Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 5/27/2016 10:35 AM, Tony Marston wrote: > I disagree completely. In a database system there is no rule that says > an object can only hold data from a single row otherwise Martin Fowler,= > the author of PoEE, would not have patterns that hold data from several= > rows. When I instantiate one of my table classes it is a valid but empt= y > object. There are two actions I can perform - inject data from the > client via the $_POST array, or tell it to retrieve data from the > database. This may involve just a single row, or multiple rows. When > reading from the database it may even result in zero rows. >=20 Yes?!? That is how everybody does it. On 5/27/2016 10:35 AM, Tony Marston wrote: > You are trying to change the language to suit the way that you work > without considering the fact that your way is not the only way and this= > change may not suit the way that others work. As far as I can see this > proposal not only does not solve a genuine problem, it adds levels of > complexity that will do nothing but increase the WTF! factor for untold= > numbers of programmers who have been happily using the language for yea= rs. >=20 Oh come on, this story again? Please, just keep on using PHP in the way you like it without making use of these new features. Nothing is changing and if all your problems are solved, good. And please, please don't start the PHP 5.2 was so much better discussion now and claiming that we all are incapable programmers. We know it by now. ;) --=20 Richard "Fleshgrinder" Fussenegger --11TdTubKw3mMChWUoFT6qvihHbe1CmR8i-- --ngOwas2EDd0tpdCpf9pfKQPlAIxGS2UQI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXSArCAAoJEOKkKcqFPVVrh8cQAJeK+u6rCCX0PXMom7ltBVZt 5UsSZl951ijrYmW/jH71IGGucg5mT65/I3/bm0KqkwsmlVyWv+uV4pweWrVzk0qV K6mRQrj0SFOZ34URdYSo0Tsx3xPVtWHzlYchK1zain18vQwLpyZOoVToL7qPHz6N bJCgJVClqLVYf6dUcu5SBx+IwhAclTJzUpn/y549R0tOfWfTZwpEjNjKmTawIi+h 4J1Fe2ndIESBPOjOTVmQaNk2+dWvEBZvQHQQ9ciNqR7L+d7e6xhDAKpsFfAusH7K AIIUw10ayLjTDcAqr4UuuBAJZtWikF0F5oQvk7cvGRhA2zM+4lWv0V/SY4xtwMX9 xhRqEaur0ncNJvVg5iRm6B8GwTgekSSm20Z07p/ktUD4VWiNdEbRCwdbuZkA9wbn VBi79K6/Z4F9GTTuQD6+fXhnKz4o1BucT8xoXIQJyZqVeX7/bbgt/+TDOXWlLaQs D9VMJkozYYCk8LZtLUPm9QBRuSfSvh3sjOsCjbasEpjJMVfKsl+zYZuaCl5OGW0k 8iYe3SSBf9VEi2zuiaTCBoMxr8Vph+maAhm3o8clTM5qrE8yNPch1oiLQ/OKEqgw 65sWpnRSGW9yzU7fnxroysdrClIMfN48mdflfd+ye3E+mcNiGhGnzU0ljdZvXT6U 4kC3nhy6/LpU4Z2Ae66V =Q/Yh -----END PGP SIGNATURE----- --ngOwas2EDd0tpdCpf9pfKQPlAIxGS2UQI--