diff options
author | 2015-05-17 14:22:14 -0400 | |
---|---|---|
committer | 2015-05-17 14:22:14 -0400 | |
commit | 2cbe3cb8c2077000e5a219e6610066659c42aa66 (patch) | |
tree | 9a46abc74ef6653d4dbf49e51bde16c29f8411d7 | |
parent | d2815d1a987e530a4ba927c59b1bb051a9836b82 (diff) |
comment typos
-rw-r--r-- | Utility/LockFile/Windows.hs | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Utility/LockFile/Windows.hs b/Utility/LockFile/Windows.hs index eff129cee..3c680d91c 100644 --- a/Utility/LockFile/Windows.hs +++ b/Utility/LockFile/Windows.hs @@ -30,8 +30,8 @@ lockShared = openLock fILE_SHARE_READ - a shared or exclusive lock. - - Note that exclusive locking also prevents the file from being opened for - - read or write by any other progess. So for advisory locking of a file's - - content, a different LockFile should be used. -} + - read or write by any other process. So for advisory locking of a file's + - content, a separate LockFile should be used. -} lockExclusive :: LockFile -> IO (Maybe LockHandle) lockExclusive = openLock fILE_SHARE_NONE @@ -47,7 +47,7 @@ lockExclusive = openLock fILE_SHARE_NONE - much more expensive, so is not done here. Thus, the use of c_CreateFile. - - Also, passing Nothing for SECURITY_ATTRIBUTES ensures that the lock file - - is not inheerited by any child process. + - is not inherited by any child process. -} openLock :: ShareMode -> LockFile -> IO (Maybe LockHandle) openLock sharemode f = do |