[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [office-formula] LOOKUP function
Hi Kohei, On Monday, 2008-02-25 11:30:17 -0500, Kohei Yoshida wrote: > * 3-parameter case ([lookup value], [lookup matrix], [result > matrix(vector)]) Um, you wrote the syntax with every parameter being optional, that's probably not intended? > > 2) The directions of the lookup matrix and the result matrix can > differ. [NOTE: the ODFF spec does not mention this.] Just to make sure that I find the right wording while editing the spec: If the lookup matrix is a row vector or square or taller than wide, and the result vector is a column vector, then the value corresponding offset-wise is returned. Same if the lookup matrix is wider than tall and the result vector is a row vector. Or could someone come up with a less confusing wording? > 3) The lengths of the search vector and the result vector do not need > to be identical; however, when the match position falls outside > the length of the result vector, an error is raised if the result > vector is given as an array object. If it's a cell range, it gets > automatically extended to the length of the searched vector. But in the direction of the result vector, as I just found out. And: if just a single cell reference is passed, a column vector is generated. > If the cell range cannot be extended due to size limit, then '0' > is displayed. How odd.. Eike -- Automatic string conversions considered dangerous. They are the GOTO statements of spreadsheets. --Robert Weir on the OpenDocument formula subcommittee's list.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]