php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #54076 Feature request - function array_walk_recursive
Submitted: 2011-02-22 21:56 UTC Modified: 2021-08-31 10:26 UTC
From: Tor-Martin at storsletten dot com Assigned: cmb (profile)
Status: Wont fix Package: Arrays related
PHP Version: 5.3.5 OS: All
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If this is not your bug, you can add a comment by following this link.
If this is your bug, but you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: Tor-Martin at storsletten dot com
New email:
PHP Version: OS:

 

 [2011-02-22 21:56 UTC] Tor-Martin at storsletten dot com
Description:
------------
---
From manual page: http://www.php.net/function.array-walk-recursive#Parameters
---

This function does not send arrays to the callback function, and in most cases this is what you want, but sometimes you may need at least the keys of the arrays (example below). My suggestion is to add a fourth parameter to this function which takes a boolean value, and defaults to FALSE. The callback function can then handle the arrays and their keys if this parameter is set to TRUE.

One usage for this feature would be if you want to make a custom function for serializing an array and all its content. A serialized string must contain the keys of child arrays, else the custom unserializer will be unable to restore child arrays properly. A custom serializer may be able to make binary strings rather than human-readable strings like serialize() does, which will save a lot of space e.g. when storing $_SESSION data in a database.

Additionally, this feature would also allow custom output of arrays in a human-friendly way, especially if the callback function can get the depth of the iteration (see the code example below).

Test script:
---------------
function awr_callback(&$val, &$key, &$ptr, $depth = 0) {
 $indent = str_pad('', $depth, ' ');
 if (is_array($val)) $ptr[0] .= "${indent}Array '$key' (" . count($val) . "):\n";
 elseif (is_string($val)) $ptr[0] .= "${indent}String '$key' (" . strlen($val) . "): $val\n";
 // ...
}

$a = array('beginning', 'first child' => array('an element', 'another element'), 'end');
$s = '';
array_walk_recursive($a, 'awr_callback', array(&$s), true);
echo $s;

// This short example is written to demonstrate usage of the suggested features, and will not work with the current version of PHP.

Expected result:
----------------
Expected output when/if the features are implemented:

String '0' (9): beginning
Array 'first child' (2):
 String '0' (10): an element
 String '1' (15): another element
String '1' (3): end

Actual result:
--------------
Actual output (if you first remove the fourth input parameter when calling array_walk_recursive):

String '0' (9): beginning
String '0' (10): an element
String '1' (15): another element
String '1' (3): end

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2021-08-31 10:26 UTC] cmb@php.net
-Status: Open +Status: Wont fix -Assigned To: +Assigned To: cmb
 [2021-08-31 10:26 UTC] cmb@php.net
This doesn't look like it would be needed that often, that it is
not better implemented in userland, and the lack of comments and
upvotes seems to confirm that.  Thus, I'm closing as WONTFIX.

If you're still interested in this feature, please pursue the RFC
process[1].

[1] <https://wiki.php.net/rfc/howto>
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Apr 25 02:01:30 2024 UTC