diff options
Diffstat (limited to 'src/tools/tqmutex_unix.cpp')
| -rw-r--r-- | src/tools/tqmutex_unix.cpp | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/src/tools/tqmutex_unix.cpp b/src/tools/tqmutex_unix.cpp index 9c793a02d..af916e3e0 100644 --- a/src/tools/tqmutex_unix.cpp +++ b/src/tools/tqmutex_unix.cpp @@ -61,7 +61,7 @@ typedef pthread_mutex_t Q_MUTEX_T; class TQRealMutexPrivate : public TQMutexPrivate { public: - TQRealMutexPrivate(bool = FALSE); + TQRealMutexPrivate(bool = false); void lock(); void unlock(); @@ -140,15 +140,15 @@ bool TQRealMutexPrivate::trylock() int ret = pthread_mutex_trylock(&handle); if (ret == EBUSY) { - return FALSE; + return false; } else if (ret) { #ifdef QT_CHECK_RANGE tqWarning("Mutex trylock failure: %s", strerror(ret)); #endif - return FALSE; + return false; } - return TRUE; + return true; } int TQRealMutexPrivate::type() const @@ -258,8 +258,8 @@ int TQRealMutexPrivate::level() /*! Constructs a new mutex. The mutex is created in an unlocked state. - A recursive mutex is created if \a recursive is TRUE; a normal - mutex is created if \a recursive is FALSE (the default). With a + A recursive mutex is created if \a recursive is true; a normal + mutex is created if \a recursive is false (the default). With a recursive mutex, a thread can lock the same mutex multiple times and it will not be unlocked until a corresponding number of unlock() calls have been made. @@ -305,8 +305,8 @@ void TQMutex::unlock() } /*! - Returns TRUE if the mutex is locked by another thread; otherwise - returns FALSE. + Returns true if the mutex is locked by another thread; otherwise + returns false. \warning Due to differing implementations of recursive mutexes on various platforms, calling this function from the same thread that @@ -321,8 +321,8 @@ bool TQMutex::locked() /*! Attempt to lock the mutex. If the lock was obtained, this function - returns TRUE. If another thread has locked the mutex, this - function returns FALSE, instead of waiting for the mutex to become + returns true. If another thread has locked the mutex, this + function returns false, instead of waiting for the mutex to become available, i.e. it does not block. If the lock was obtained, the mutex must be unlocked with unlock() |
