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/encoder/core/src/slice_multi_threading.cpp (1 of 22 files). Show all

Unified · Split

codec/encoder/core/src/slice_multi_threading.cpp+2−2

@@ -967,7 +967,7 @@ WELS_THREAD_ROUTINE_TYPE CodingSliceThreadProc (void* arg) { · 966 unmodified lines
967	967	InitBits (&pSliceBs->sBsWrite, pSliceBs->pBsBuffer, pSliceBs->uiSize);
968	968
969	969	#if MT_DEBUG_BS_WR
970		− pSliceBs->bSliceCodedFlag = FALSE;
	970	+ pSliceBs->bSliceCodedFlag = false;
971	971	#endif//MT_DEBUG_BS_WR
972	972
973	973	if (bNeedPrefix) {
@@ -1041,7 +1041,7 @@ WELS_THREAD_ROUTINE_TYPE CodingSliceThreadProc (void* arg) { · 67 unmodified lines
1041	1041	#endif//SLICE_INFO_OUTPUT
1042	1042
1043	1043	#if MT_DEBUG_BS_WR
1044		− pSliceBs->bSliceCodedFlag = TRUE;
	1044	+ pSliceBs->bSliceCodedFlag = true;
1045	1045	#endif//MT_DEBUG_BS_WR
1046	1046
1047	1047	#ifdef _WIN32

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