Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21711 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93582 invoked by uid 1010); 28 Jan 2006 03:24:13 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 93567 invoked from network); 28 Jan 2006 03:24:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2006 03:24:13 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:56909] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 8C/4F-03249-CD3EAD34 for ; Fri, 27 Jan 2006 22:24:13 -0500 Received: from [192.168.1.3] (dslb-084-063-025-088.pools.arcor-ip.net [84.63.25.88]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 033FC35C1C1; Sat, 28 Jan 2006 04:24:08 +0100 (CET) Date: Sat, 28 Jan 2006 04:26:19 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1278071903.20060128042619@marcus-boerger.de> To: Jeff Moore Cc: php internals In-Reply-To: <3d6d6f6b845095f44028f43b3bdca08d@procata.com> References: <1fa2fe9192c4d0ed1f9037abd06d6b14@procata.com> <15310483413.20060127191050@marcus-boerger.de> <3d6d6f6b845095f44028f43b3bdca08d@procata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] SplObjectStorage From: helly@php.net (Marcus Boerger) Hello Jeff, what the hell do you want? Friday, January 27, 2006, 8:23:26 PM, you wrote: > Hi, Marcus, > On Jan 27, 2006, at 1:10 PM, Marcus Boerger wrote: >> yes, it is a conainer and not a set. > So why not call it a container instead of storage? >> And it cannot take anything other >> than php objects. That's why. > SplObjectContainer? > But, then, it has that uniqueness constraint. The SplObjectStorage > name doesn't convey that idea at all. > SplUniqueObjectContainer? > From an API standpoint (rather than an implementation standpoint), I > don't understand the need for the object only constraint in PHP. > SplUniqueZvalContainer? > SplUniqueValueContainer? > SplUniqueMemberContainer? > Yours, > Jeff Best regards, Marcus