1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

QMutex: small doc fixes

Browse Source 
Add parentheses after function names, replace
  is different -> differs

Change-Id: I6332db1d1650ed8d8320c5f20cd79d0bf1870e27
Reviewed-by: Mitch Curtis <mitch.curtis@qt.io>
This commit is contained in:
Marc Mutz 2016-11-29 10:02:44 +01:00
parent 947cace799
commit 1710947fde
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/corelib/thread/qmutex.cpp
View File

@ -279,7 +279,7 @@ bool QMutex::tryLock(int timeout) QT_MUTEX_LOCK_NOEXCEPT
for the mutex to become available. for the mutex to become available.
Note: Passing a negative duration as the \a duration is equivalent to Note: Passing a negative duration as the \a duration is equivalent to
calling try_lock(). This behavior is different from tryLock. calling try_lock(). This behavior differs from tryLock().
If the lock was obtained, the mutex must be unlocked with unlock() If the lock was obtained, the mutex must be unlocked with unlock()
before another thread can successfully lock it. before another thread can successfully lock it.
@ -303,7 +303,7 @@ bool QMutex::tryLock(int timeout) QT_MUTEX_LOCK_NOEXCEPT
for the mutex to become available. for the mutex to become available.
Note: Passing a \a timePoint which has already passed is equivalent Note: Passing a \a timePoint which has already passed is equivalent
to calling try_lock. This behavior is different from tryLock. to calling try_lock(). This behavior differs from tryLock().
If the lock was obtained, the mutex must be unlocked with unlock() If the lock was obtained, the mutex must be unlocked with unlock()
before another thread can successfully lock it. before another thread can successfully lock it.