shithub: openh264

Download patch

ref: a1b8ffc9dfbebaf8961dc8c0e3f90e8e8866e483
parent: a852ac99edac9a95f1d89009b12cfa6094dd9e53
author: Martin Storsjö <martin@martin.st>
date: Fri Jan 16 05:29:41 EST 2015

Use the right data type for a variable

There is little point in using an int32_t variable for something
that will only be used for passing in as a bool parameter to a
function.

--- a/test/encoder/EncUT_MotionEstimate.cpp
+++ b/test/encoder/EncUT_MotionEstimate.cpp
@@ -250,7 +250,7 @@
   SWelsFuncPtrList sFuncList;
   SWelsME sMe;
   SSlice sSlice;
-  int32_t iUsageType = 1;
+  bool bUsageType = true;
   uint8_t* pRef = m_pRefStart + PADDING_LENGTH * m_iWidthExt + PADDING_LENGTH;
   const int32_t kiMaxBlock16Sad = 72000;//a rough number
 
@@ -257,7 +257,7 @@
   memset (&sSlice, 0, sizeof (sSlice));
   memset (&sMe, 0, sizeof (sMe));
   WelsInitSampleSadFunc (&sFuncList, 0); //test c functions
-  WelsInitMeFunc (&sFuncList, 0, iUsageType);
+  WelsInitMeFunc (&sFuncList, 0, bUsageType);
 
   RandomPixelDataGenerator (m_pSrc, m_iWidth, m_iHeight, m_iWidth);
   RandomPixelDataGenerator (m_pRefStart, m_iWidthExt, m_iHeightExt, m_iWidthExt);