Use the C++ constants true/false instead of defining our own

TRUE/FALSE has intentionally been left in use for the few platform specific APIs that define these constants themselves and expect them to be used, for consistency.

Martin Storsjö committed 12 years ago

Commit 80862ee1 parent f2bd22a22 files · +123 −136Browse files

Showing the changes to codec/decoder/core/src/deblocking.cpp (1 of 22 files). Show all

Unified · Split

codec/decoder/core/src/deblocking.cpp+2−2

@@ -252,8 +252,8 @@ int32_t DeblockingAvailableNoInterlayer (PDqLayer pCurDqLayer, int32_t iFilterId · 251 unmodified lines
252	252	int32_t iMbY = pCurDqLayer->iMbY;
253	253	int32_t iMbX = pCurDqLayer->iMbX;
254	254	int32_t iMbXy = pCurDqLayer->iMbXyIndex;
255		− bool bLeftFlag = FALSE;
256		− bool bTopFlag = FALSE;
	255	+ bool bLeftFlag = false;
	256	+ bool bTopFlag = false;
257	257
258	258	if (2 == iFilterIdc) {
259	259	bLeftFlag = (iMbX > 0) && (pCurDqLayer->pSliceIdc[iMbXy] == pCurDqLayer->pSliceIdc[iMbXy - 1]);

Use the C++ constants true/false instead of defining our own

Keyboard shortcuts

General

Issues and pull requests

Issues, pull requests and Inbox

Repository code