History

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/svc_encode_slice.cpp (1 of 22 files). Show all

Unified · Split

codec/encoder/core/src/svc_encode_slice.cpp+2−2
@@ -874,7 +874,7 @@ bool DynSlcJudgeSliceBoundaryStepBack (void* pCtx, void* pSlice, SSliceCtx* pSli · 873 unmodified lines
874874 WelsMutexUnlock (&pEncCtx->pSliceThreading->mutexSliceNumUpdate);
875875 #endif//MT_ENABLED
876876
877− return TRUE;
877+ return true;
878878 }
879879
880880 if (
@@ -896,7 +896,7 @@ bool DynSlcJudgeSliceBoundaryStepBack (void* pCtx, void* pSlice, SSliceCtx* pSli · 15 unmodified lines
896896 WelsMutexUnlock (&pEncCtx->pSliceThreading->mutexSliceNumUpdate);
897897 #endif//MT_ENABLED
898898
899− return FALSE;
899+ return false;
900900 }
901901
902902 ///////////////

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t