diff options
| author | Tor Lillqvist <tml@collabora.com> | 2014-07-08 02:35:00 +0300 |
|---|---|---|
| committer | Tor Lillqvist <tml@collabora.com> | 2014-07-08 02:37:37 +0300 |
| commit | 1a400f39e8cb23b316565dd116b194a99689630d (patch) | |
| tree | bdea2319198bea134e28520f42cd7e6c59ecfeb3 /configmgr | |
| parent | ab740f43d0a3b96a719d13f28a427d20a4da0e2b (diff) | |
WaE: Unreachable code
Not sure if the intent is that clearCache() should be called, but the
calls have just accidentally been placed after the return statements,
or whether the code works correctly and as intended as it is now,
i.e. with the unreachable calls to clearCache().
Warning emitted by VS 2013, why don't other compilers warn? Perhaps
these functions are never called?
Change-Id: I16b0bc1b836753ef5579dadba211cbce4f50cbc3
Diffstat (limited to 'configmgr')
| -rw-r--r-- | configmgr/source/nodemap.hxx | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/configmgr/source/nodemap.hxx b/configmgr/source/nodemap.hxx index 068a471c670f..dcfac2bc4441 100644 --- a/configmgr/source/nodemap.hxx +++ b/configmgr/source/nodemap.hxx @@ -52,8 +52,8 @@ class NodeMap iterator end() { return maImpl.end(); } const_iterator end() const { return maImpl.end(); } - rtl::Reference<Node> &operator[](const OUString &aStr) { return maImpl[aStr]; clearCache(); } - std::pair<iterator,bool> insert(const value_type &vt) { return maImpl.insert(vt); clearCache(); } + rtl::Reference<Node> &operator[](const OUString &aStr) { return maImpl[aStr]; /* clearCache(); */ } + std::pair<iterator,bool> insert(const value_type &vt) { return maImpl.insert(vt); /* clearCache(); */ } void clear() { maImpl.clear(); clearCache(); } void erase(const iterator &it) { maImpl.erase(it); clearCache(); } void erase(const OUString &aStr) { maImpl.erase(aStr); clearCache(); } |