Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:102269 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26982 invoked from network); 14 Jun 2018 22:27:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jun 2018 22:27:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=enno.woortmann@web.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=enno.woortmann@web.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain web.de designates 217.72.192.78 as permitted sender) X-PHP-List-Original-Sender: enno.woortmann@web.de X-Host-Fingerprint: 217.72.192.78 mout.web.de Received: from [217.72.192.78] ([217.72.192.78:57809] helo=mout.web.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CB/7F-29356-7CBE22B5 for ; Thu, 14 Jun 2018 18:27:20 -0400 Received: from [192.168.0.48] ([77.21.86.66]) by smtp.web.de (mrweb103 [213.165.67.124]) with ESMTPSA (Nemesis) id 0Mg7Dt-1fqurG1NGX-00NQX6; Fri, 15 Jun 2018 00:27:15 +0200 To: "Christoph M. Becker" , internals@lists.php.net References: <75db877c-ef0b-7d3b-48a8-9879d90352b0@web.de> <6ec97c5a-3790-2391-6232-d0cc2d36b9c3@gmx.de> Message-ID: <9db5a21b-2801-3db5-44ae-d03f1e531deb@web.de> Date: Fri, 15 Jun 2018 00:27:19 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <6ec97c5a-3790-2391-6232-d0cc2d36b9c3@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Antivirus: Avast (VPS 180613-2, 13.06.2018), Outbound message X-Antivirus-Status: Clean X-Provags-ID: V03:K1:Q23J2p39dBzGZcUbH9Joe9ErNAFfE5P6qWuB+hR6UinZU2Ju7U9 CZ/I50hT6u7pFqKKoemPQeLj60rQFGJ/AH0CO/Ww4virJXlGJOIXJt7tC+xAEffM42D+PDS wRxdZyzxx6lxg+rlDpGbT0tu5JqTsdilvX/WO2xcjD8oH7aID/W6PrY//zdPlHcv7X167p0 EUSswV77eHEiUUZxzdYZg== X-UI-Out-Filterresults: notjunk:1;V01:K0:kMCXii++nl4=:Wcu8n+dlusqGlbGMsIg1ue JYenBFYcGYBgVJYL6Ls4TXHLZmPyiuDx2I1ixUIFCXSqQDUDqEhIVQCOYMIKPZP786GVaCmD+ RmmUi4O17DjfvZmrH1ozAdN7aEM0/f4Gy24vkYQl59angvfhlXggbCNtyhZYTh49fAOcca3Lo fdL4SjgaKQGtmz6CUdScU51Hwi6Kr3gKziU9tIR1NY09VDoy+nPsEMspMync8YSyl/NKbBnhd NfGfa0QZod3RBE9XAkvNy6wEHnkfys/+nq53J4CqAHbDj1aUkwgmZ7wsXm1bOwx8Ja2y2zHEG jnWWltHWkmN2R3Jh9uteg71S3aGUM2e2X1vFRE0VLru5MmqrMqrXB4LQ2i/++rKOHQhcS2AcM gb23LSP2BVil7aD6Q2juyCkNYD/EvOABD3GHx0+wOz9HdX8qNxDHQFQQ70IyWR31aayqZKGuL JuaEAoIT1+NeJqhXzVKA5oPeEmEAuNDKR9XaNod5yO8RjkzxVSrV8KKsIppeEBlvfguQVS5H3 p6vYFu97kVfMqoA+VcyMkB5AmogOw9aLZKtWcPqItUlJQKRfL6ZcB2xM7U9WirQ58i2QTH4eG vFOX2egR3sR5NjTelB3c0rEbQS9UIu7t3F5C1fwO5QKui0SbKlBvfrjINeIB+CA+AsUM8umcN 31slnZBcJPEyxQeJlUNE/j4HCBrZnxz+o6Z08NseNUVE8WREvgvKBHN2DeaqYGE1AifQdCLK/ 90AT8tp+l4SppqTzBy5gYBzLyL8qcr8K7VtjALRGuDhGI5av9PqPjt06PvEEgMpKZA2ai9KBh dKsSRaV Subject: Re: [RFC][Under Discussion] Add functions array_key_first() and array_key_last() From: enno.woortmann@web.de (Enno Woortmann) Hi, On 13.06.2018 at 23:10, Christoph M. Becker wrote: > I suggest to address C=C3=B4me's suggestion[1] on this mailing list and= > especially in the RFC (the template[2] offers =E2=80=9COpen Issues=E2=80= =9D and > =E2=80=9CRejected Features=E2=80=9D sections). > > [1] > I've added the "Open Issues" section to the RFC and added the idea of C=C3= =B4me and Gabriel to add the corresponding functions for handling the val= ues of the outer elements of an array to provide a complete set of functi= ons. Currently I see three possibilities to handle the idea. Either extend the= scope of the RFC to cover also the handling of the values, which could b= e implemented rather fast and by reusing a lot of code as the current imp= lementation already gathers the bucket for the first/last element of an a= rray, or move this idea to a future scope which should be covered by a se= parate RFC. The third alternative would be to skip the implementation of = the corresponding functions. In my opinion it's a good idea to complete the function set by also provi= ding functions for the handling of array values. Both opportunities which= would lead to the completed set are practicable in my view. Any opinions concerning this issue? Good night (or day, wherever you are ;) ), Enno