rfc:array_part

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
rfc:array_part [2012/05/21 17:29] – no recursion prohibition cataphractrfc:array_part [2017/09/22 13:28] (current) – external edit 127.0.0.1
Line 3: Line 3:
   * Date: 2012-05-14   * Date: 2012-05-14
   * Author: Gustavo Lopes <cataphract@php.net>   * Author: Gustavo Lopes <cataphract@php.net>
-  * Status: Under Discussion+  * Status: Declined
   * First Published at: http://wiki.php.net/rfc/array_part   * First Published at: http://wiki.php.net/rfc/array_part
  
Line 25: Line 25:
 Each part specification shall have one of the following forms: Each part specification shall have one of the following forms:
  
-  * A sequential numeric array of indexes, which specifies that only the elements existing at those indexes will be kept.+  * A non-empty sequential numeric array of indexes, which specifies that only the elements existing at those indexes will be kept.
   * A single index, which specifies that only the element existing at that index will be kept. In this case the level will be collapsed onto the previous one, meaning all the arrays at that level will be replaced with its element the specified index.   * A single index, which specifies that only the element existing at that index will be kept. In this case the level will be collapsed onto the previous one, meaning all the arrays at that level will be replaced with its element the specified index.
   * A span part specification is an associative array. The following keys are allowed //start//, //end// and //step//. At least //start// or //end// must be specified. //start// and //end// are an index or a special value -- ''null''. //step// is a non-zero integer, defaulting to ''1''. If ''start'' or ''end'' are not specified, they default to ''null'', which refer to either the first or last element depending on the sign of //step//. If //step// is +-1 and //start// and //end// are both ''null'' (or, if ''$indexesAreKeys'' is ''false'', //start// and //end// are //0// and //-1// or vice-versa depending on the sign of //step//), then we say the span encompasses all elements on that level (possibly 0).   * A span part specification is an associative array. The following keys are allowed //start//, //end// and //step//. At least //start// or //end// must be specified. //start// and //end// are an index or a special value -- ''null''. //step// is a non-zero integer, defaulting to ''1''. If ''start'' or ''end'' are not specified, they default to ''null'', which refer to either the first or last element depending on the sign of //step//. If //step// is +-1 and //start// and //end// are both ''null'' (or, if ''$indexesAreKeys'' is ''false'', //start// and //end// are //0// and //-1// or vice-versa depending on the sign of //step//), then we say the span encompasses all elements on that level (possibly 0).
Line 37: Line 37:
   * If ''$indexesAreKeys'' is ''true'' then an element is at //i// if its array key is //i//.   * If ''$indexesAreKeys'' is ''true'' then an element is at //i// if its array key is //i//.
  
-The keys in the original array are not preserved in the output, expect at levels that were not visited. References are preserved.+The keys in the original array are not preserved in the output, expect at levels that were not visited. References are not preserved when the elements are added to the resulting array.
  
 This function shall return ''false'' upon finding error conditions. The following are error conditions: This function shall return ''false'' upon finding error conditions. The following are error conditions:
Line 43: Line 43:
   * Giving arguments with different PHP types from those specified.   * Giving arguments with different PHP types from those specified.
   * Giving malformed part specifications (where the individual elements do not follow the syntactic rules given here).   * Giving malformed part specifications (where the individual elements do not follow the syntactic rules given here).
-  * Specifying an part index than does not exist at at least of the elements at the level the part refers to: (e.g. ''%%array_part([[1],[1,2]],   [['start'=>0, 'end'=>-1], 1])%%'' is an error condition, because while ''1'' is a valid index for ''%%[1,2]%%'', it is not so for ''%%[[1]]%%''). However, span part specifications that comprise all elements are always accepted.+  * Specifying an part index than does not exist in at least one of the elements at the level the part refers to: (e.g. ''%%array_part([[1],[1,2]],   [['start'=>0, 'end'=>-1], 1])%%'' is an error condition, because while ''1'' is a valid index for ''%%[1,2]%%'', it is not so for ''%%[[1]]%%''). However, span part specifications that comprise all elements are always accepted.
   * Giving a part specification with levels that do not exist in the input. This does not apply if, as a result of a span part that comprises all the elements of that level and at the level before existed only empty arrays, no elements were left for the next level. For instance '%%array_part([], [['start'=>0, 'end'=>-1]])%%' is valid, as is '%%array_part([[]], [0, ['start'=>0, 'end'=>-1], 1, 2, 3])%%', which will return ''%%[[]]%%''.   * Giving a part specification with levels that do not exist in the input. This does not apply if, as a result of a span part that comprises all the elements of that level and at the level before existed only empty arrays, no elements were left for the next level. For instance '%%array_part([], [['start'=>0, 'end'=>-1]])%%' is valid, as is '%%array_part([[]], [0, ['start'=>0, 'end'=>-1], 1, 2, 3])%%', which will return ''%%[[]]%%''.
  
Line 57: Line 57:
  
 [[https://gist.github.com/2660601#file_test.php|Direct link to the tests]] [[https://gist.github.com/2660601#file_test.php|Direct link to the tests]]
 +
 +===== Comments =====
 +I would find this far more useful if the keys were preserved, or at least an option to do so.
 +Or the old standby that INT keys get renumbered but non-INT do not.
 +
  
 ===== Objections ===== ===== Objections =====
Line 73: Line 78:
  
 This is true. We must traverse the array from the start or the end to get to the n-th element. That's just the way PHP arrays are implemented. However, if you have numeric sequential arrays, you can use ''$indexesAreKeys = true'' to access the n-th element without this penalty (also note that the sample implementation is **not** optimized). This is true. We must traverse the array from the start or the end to get to the n-th element. That's just the way PHP arrays are implemented. However, if you have numeric sequential arrays, you can use ''$indexesAreKeys = true'' to access the n-th element without this penalty (also note that the sample implementation is **not** optimized).
 +
 +===== Vote =====
 +
 +<doodle 
 +title="Should the current array_part() implementation be merged" auth="cataphract" voteType="single" closed="False">
 +   * Yes
 +   * No
 +</doodle>
  
 ===== Changelog ===== ===== Changelog =====
Line 78: Line 91:
   * 2012-05-14 Initial version   * 2012-05-14 Initial version
   * 2012-05-21 Dropped recursion restriction, added note on how references are preserved, added link to native implementation   * 2012-05-21 Dropped recursion restriction, added note on how references are preserved, added link to native implementation
- +  * 2012-05-21 References are not preserved after all 
 +  * 2012-05-28 Vote opened
  
rfc/array_part.1337621345.txt.gz · Last modified: 2017/09/22 13:28 (external edit)

Page Tools