3D Ranges appear to be broken
Submitted by an unknown user
Link to original bug (#569372)
Description
The formula
=vlookup(7,ThreeD1!C1:ThreeD2!D6,2)
gets evaluated as-if the middle range was just ThreeD1!C1:C6.
The expression gets parsed as a range ctor of ThreeD1!C1 and ThreeD2!D6. Note, that gnm_expr_range_op never uses b_start.
Also, in this case the ranges are constant. Do we really need dynamic dependencies for this? I would assume that we could simply create the 3D cell range as parse time. (But note, that the ctor also is made on xls import.)
Version: git master