From b2345f6d18ae6787fa6f05a3431e75f6810f83fc Mon Sep 17 00:00:00 2001 From: Lionel Elie Mamane Date: Thu, 19 Jan 2012 17:54:10 +0100 Subject: janitorial: don't rely on detail of current OSL_ENSURE implementation As in: that the compiler won't see the variables in the condition when OSL_DEBUG_LEVEL==0 --- dbaccess/source/core/api/RowSetBase.cxx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'dbaccess') diff --git a/dbaccess/source/core/api/RowSetBase.cxx b/dbaccess/source/core/api/RowSetBase.cxx index f3ca25084cee..728934b8ac8a 100644 --- a/dbaccess/source/core/api/RowSetBase.cxx +++ b/dbaccess/source/core/api/RowSetBase.cxx @@ -1128,8 +1128,8 @@ void ORowSetBase::setCurrentRow( sal_Bool _bMoved, sal_Bool _bDoNotify, const OR positionCache( MOVE_NONE_REFRESH_ONLY ); #if OSL_DEBUG_LEVEL > 0 sal_Int32 nNewRow = m_pCache->getRow(); -#endif OSL_ENSURE(nOldRow == nNewRow,"Old position is not equal to new postion"); +#endif m_aCurrentRow = m_pCache->m_aMatrixIter; m_bIsInsertRow = sal_False; OSL_ENSURE(!m_aCurrentRow.isNull(),"CurrentRow is nul after positionCache!"); -- cgit