summaryrefslogtreecommitdiff
path: root/sc/source
diff options
context:
space:
mode:
authorEike Rathke <erack@redhat.com>2016-05-21 00:20:03 +0200
committerEike Rathke <erack@redhat.com>2016-05-21 00:21:23 +0200
commitccf99226447e82b8b6ebb6167c5607d19913b091 (patch)
tree1cb3c0ead892b3f000e9c57fbfd0b30960abae05 /sc/source
parent01e76ceb2e22ccf9a61789aef1fe982332b777bb (diff)
document findings on external range reference handling
Change-Id: Ib9f3bdb41d8fc8b3c370508675b39a331f5ba0a1
Diffstat (limited to 'sc/source')
-rw-r--r--sc/source/core/tool/interpr1.cxx6
1 files changed, 6 insertions, 0 deletions
diff --git a/sc/source/core/tool/interpr1.cxx b/sc/source/core/tool/interpr1.cxx
index b2b19f1d0468..1a24e78828aa 100644
--- a/sc/source/core/tool/interpr1.cxx
+++ b/sc/source/core/tool/interpr1.cxx
@@ -878,6 +878,12 @@ double ScInterpreter::Compare( ScQueryOp eOp )
break;
case svExternalDoubleRef:
// TODO: Find out how to handle this...
+ // Xcl generates a position dependent intersection using
+ // col/row, as it seems to do for all range references, not
+ // only in compare context. We'd need a general implementation
+ // for that behavior similar to svDoubleRef in scalar and array
+ // mode. Which also means we'd have to change all places where
+ // it currently is handled along with svMatrix.
default:
SetError( errIllegalParameter);
break;