Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78380 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19805 invoked from network); 27 Oct 2014 08:33:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Oct 2014 08:33:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.177 as permitted sender) X-PHP-List-Original-Sender: mike.php.net@gmail.com X-Host-Fingerprint: 209.85.212.177 mail-wi0-f177.google.com Received: from [209.85.212.177] ([209.85.212.177:55476] helo=mail-wi0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F2/4A-56216-D630E445 for ; Mon, 27 Oct 2014 03:33:50 -0500 Received: by mail-wi0-f177.google.com with SMTP id ex7so5674636wid.10 for ; Mon, 27 Oct 2014 01:33:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=TF0i9VZqz1Mz16KAguDzskJ37siFhfWPWBGG7ZgQoD8=; b=mrx2ujcVpIVBL03wZvJOQicj9evCDJyjgDxXBJwc0WDUGwiJBIa78OmG6XRSgAYHmT DLfWiP2bizN7DwRHFgVC1HzU+stJO3ZCce8mmNtVuSZbeKUyz8O2YOOLPPMFRg6oP2HA /LSZG2vjqStA3WYZ5+gfM/Tv4IJ3xH2Vqp8gG6SgJ9B+OQYcIKBSqTqD4mc6d3Swz0O5 Kack6hs2O1MlGjVEUACjZ9+ylCcTrAiS+NNkUSwEnoCu5Fu0Ww/omOJTBncrWv0r/I+w V6qoCrNKmBELY6IftGBj9I9Mx2sJ8C4JfZPXGtac3+oNhWd1zI1iWVeGUVRHBORVzdat wcYg== X-Received: by 10.180.95.74 with SMTP id di10mr1476673wib.54.1414398826633; Mon, 27 Oct 2014 01:33:46 -0700 (PDT) Received: from [192.168.1.163] (95-143-224-254.customer.bnet.at. [95.143.224.254]) by mx.google.com with ESMTPSA id da3sm14770911wjb.12.2014.10.27.01.33.45 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Oct 2014 01:33:46 -0700 (PDT) Sender: Michael Wallner Message-ID: <544E0368.5060705@php.net> Date: Mon, 27 Oct 2014 09:33:44 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Stas Malyshev , Patrick Schaaf , Stas Malyshev CC: internals References: <544DA1CD.9070109@php.net> <544DEFBE.8090107@sugarcrm.com> In-Reply-To: <544DEFBE.8090107@sugarcrm.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Using objects as keys From: mike@php.net (Michael Wallner) On 27/10/14 08:09, Stas Malyshev wrote: > Hi! > >> I don't like this, mainly because it blocks a future direct use and storage >> of objects as keys in an array, i.e. what SplObjectStorage does. > > It does not. It just allows the objects to control how they are seen > when they are used as keys in regular PHP arrays. That does not prevent > SplObjectStorage or anything else from doing whatever one wants. I > personally would say SplObjectStorage probably should respect __hash if > provided, but we can discuss it separately. Do we want to consider to let core use spl_object_hash() if ::__hash() is not implemented, so objects can always be used as keys? -- Regards, Mike