Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71321 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54069 invoked from network); 20 Jan 2014 10:55:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jan 2014 10:55:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; 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:51565] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/6A-02192-7A00DD25 for ; Mon, 20 Jan 2014 05:55:36 -0500 Received: (qmail 6854 invoked by uid 89); 20 Jan 2014 10:55:32 -0000 Received: by simscan 1.3.1 ppid: 6848, pid: 6851, t: 0.0662s 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; 20 Jan 2014 10:55:32 -0000 Message-ID: <52DD013D.2020605@lsces.co.uk> Date: Mon, 20 Jan 2014 10:58:05 +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: internals@lists.php.net References: <005001cf124f$3a40df00$aec29d00$@tutteli.ch> <20140116110127.202079vzjsj76n7b@webmail.tutteli.ch> <0B.B1.24763.139B7D25@pb1.pair.com> <002001cf12da$2bfbda90$83f38fb0$@tutteli.ch> <52DCA3E7.80602@lerdorf.com> <52DCC067.9090603@garfieldtech.com> <52DCD8B5.6060006@lerdorf.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Introducing "Array Of" RFC From: lester@lsces.co.uk (Lester Caine) Pierre Joye wrote: > As I like this RFC for other reasons (type hinting extension), I tend > to think that the use cases presented here can be done in a more > efficient way. Someone else mentioned "collections" and it is exactly > what it is all about. A collection could be an instance of a given > class, which stores only one class type. It prevents on usage/function > call checks and checks are done only when adding a member to the > collection. To my mind this is a lot more PHP friendly? ... If I am building an array of data then I have the option to create each element as a 'new' construct, or simply cache the data in a manor that a single instance of the object can handle multiple sets of data. A collection of data could potentially be managed in a single instance? -- 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