> So you can't use it as a subscript? That sounds unfriendly. Almost > every function using this will be subtly broken.
I concur; perhaps "offset" was the design intention, but it's wrong. The result should be a subscript.
do you have any idea about name for this function? array_position is ok?
+1 on array_position. It's possible at some point we'll actually want array_offset that does what it claims.
additional implementation of array_position needs few lines more
On another note, you mentioned elsewhere that it's not possible to return anything other than an integer. Why can't there be a variation of this function that returns an array of ndims-1 that is the slice where a value was found?
We talked about it, when we talked about MD searching - and we moved it to next stage.
I am thinking so array_postions can support MD arrays due returning a array
Regards
Pavel
-- Jim Nasby, Data Architect, Blue Treble Consulting Data in Trouble? Get it in Treble! http://BlueTreble.com