Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71182 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 14039 invoked from network); 16 Jan 2014 12:22:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jan 2014 12:22:05 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:33901] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4E/04-24763-3D9C7D25 for ; Thu, 16 Jan 2014 07:00:20 -0500 Received: (qmail 6831 invoked by uid 89); 16 Jan 2014 11:59:47 -0000 Received: by simscan 1.3.1 ppid: 6752, pid: 6785, t: 11.9087s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 16 Jan 2014 11:59:36 -0000 Message-ID: <52D7CA28.2010205@lsces.co.uk> Date: Thu, 16 Jan 2014 12:01:44 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23 MIME-Version: 1.0 To: PHP internals References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Introducing "Array Of" RFC From: lester@lsces.co.uk (Lester Caine) Philip Sturgeon wrote: > Everything is open for discussion, especially the current error > messages. They are not perfect, so let us know if you have better > ideas. I'm quite happy to put my hands up and say that despite having been programming since the early 70's some of these 'essential facilities' are simply going over my head. I've programmed with 'strict' languages and had to work around their restrictions in the past, so the 'loose' format of PHP used to be a pleasure. So all of these 'improvements' to keep to nibble away at the that freedom is a pain. My IDE provides all of the 'type-hinting' that I need and a lot more besides, totally outside the final code base. Many of the e_strict rules cause problems resulting in a lot of duplication of code, adding facilities which create more hinting/type checks still seems backwards. This may just be my misunderstanding the OO basis people are working on, and many of my 'objects' are persisted directly in the database, so the array of elements is simply a record from the database. That record may have a type field so that the resulting array is a mixture of types of object, but all of the same base class. As with other additions made, I don't understand where this 'improved type-hinting' fits into the general development of PHP? How much code will actually benefit from this addition, and how much will simply ignore it? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk