Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42303 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98120 invoked from network); 17 Dec 2008 18:59:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Dec 2008 18:59:05 -0000 Authentication-Results: pb1.pair.com smtp.mail=ekneuss@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ekneuss@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.46.30 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: ekneuss@gmail.com X-Host-Fingerprint: 74.125.46.30 yw-out-2324.google.com Received: from [74.125.46.30] ([74.125.46.30:58143] helo=yw-out-2324.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 81/22-19668-8FB49494 for ; Wed, 17 Dec 2008 13:59:04 -0500 Received: by yw-out-2324.google.com with SMTP id 5so19132ywb.83 for ; Wed, 17 Dec 2008 10:59:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=cjG7KHLwuzOxmRmjhhbKBHdeJoL1/SuW0w9qpWzCasc=; b=Ukt4YlPMkubqZJ+RWP1ponv6Qe86dcY7+PykUWKGFHUwK2+B2nucw/cGXWyDdmcLWj RE3hBL27kiyMRZRBMTG3rjq9zvzLEpmsTc8kvS8qAINdFcnAdCC0WPFvGwUBus+3++Xl AQsLw7LBFvcSzuPLPRAXX8Ph3hRO5CuShpsxI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=OHHdpl53XTZlqOaXMQqo7b6eRClMg06OrcPlq/NJ85drwayMkbQBWmUHqglnZ5iIXa EyUlPumWA+rEk5jFZbOPCyuFm6Kz/S8xI3wks/9jJPmRCHpyyZGADiSYIgktpEKm8kNT NmlpTyfqjO38uLya+QHsn06NfbjTdIFRuY5j0= Received: by 10.100.125.12 with SMTP id x12mr872395anc.4.1229540341354; Wed, 17 Dec 2008 10:59:01 -0800 (PST) Received: by 10.100.7.15 with HTTP; Wed, 17 Dec 2008 10:59:01 -0800 (PST) Message-ID: Date: Wed, 17 Dec 2008 19:59:01 +0100 Sender: ekneuss@gmail.com To: "Lars Strojny" Cc: "Guilherme Blanco" , "internals Mailing List" In-Reply-To: <1229538590.4955.15.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1229538590.4955.15.camel@localhost> X-Google-Sender-Auth: c5e0a05d1c472d30 Subject: Re: [PHP-DEV] New function proposal: spl_object_id From: webmaster@colder.ch ("Etienne Kneuss") Hello, On Wed, Dec 17, 2008 at 7:29 PM, Lars Strojny wrote: > Hi Guilherme, > > thanks for moving the discussion to the list. > > Am Mittwoch, den 17.12.2008, 15:31 -0200 schrieb Guilherme Blanco: > [...] >> It seems that Marcus controls the commit access to SPL. So I'm turning >> the conversation async, since I cannot find him online at IRC. >> So, can anyone review the patch, comment it and commit if approved? > > Just for clarification, it is not about access, but about maintenance. > So if Marcus gives his go, we can happily apply the patch and add a few > tests (something you could start preparing now). > > cu, Lars > Last time I checked with Marcus, there were concerns about disclosing a valid pointer to the user. I'd be happy to see a use-case where this information is really needed heavily. The only real usecase of heavy usages seems to be to implement sets of objects. but splObjectStorage is here for that precise use-case... Regards -- Etienne Kneuss http://www.colder.ch Men never do evil so completely and cheerfully as when they do it from a religious conviction. -- Pascal