On 04/12/2017 07:29 PM, Shawn H Corey wrote:
On Wed, 12 Apr 2017 18:16:56 -0400
Uri Guttman <u...@stemsystems.com> wrote:
It's not about saving time. It's about removing a bug. In the code
below, notice that there are two different outputs depending on the
order that splice is applied. It's only by using descending indexing do
you get the correct deletions.
i get that now. this is because of the need to filter based on indexes
rather than values. the hash slice ideas should still work but even then
ordering may be off due to the lack of sorting of the values (which are
the indexes of the original array of data).
it is so odd to be filtering an array by the indexes. i smell an XY
problem here. i wonder what the real goal is vs how to solve it this way.
thanx,
uri
--
To unsubscribe, e-mail: beginners-unsubscr...@perl.org
For additional commands, e-mail: beginners-h...@perl.org
http://learn.perl.org/
