Minor corrections.

This commit is contained in:
mainzelm 2003-02-27 07:31:25 +00:00
parent 0016567893
commit fd72e8f0a6
1 changed files with 6 additions and 6 deletions

View File

@ -59,7 +59,7 @@ Here is scsh's interface to dot-locking:
before it retries. If the lock cannot be obtained after
\var{retry-number} attempts, the procedure returns \sharpf,
otherwise \sharpt. The default value of \var{retry-number} is
\sharpf which corresponds to an infinite number of retires.
\sharpf{} which corresponds to an infinite number of retires.
If \var{stale-time} is non-\sharpf, it specifies the minimum age a
lock may have (in seconds) before it is considered \textit{stale}.
@ -72,7 +72,7 @@ Here is scsh's interface to dot-locking:
Note that it is possible that \ex{obtain-dot-lock} breaks a lock
but nevertheless fails to obtain it otherwise. If it is necessary
to handle this case specially, use \ex{break-dot-lock} directly
(see below) rather than specifying a non-\sharpf \var{stale-time}
(see below) rather than specifying a non-\sharpf{} \var{stale-time}
\end{desc}
\defun {break-dot-lock} {file-name} {undefined}
@ -99,10 +99,10 @@ Here is scsh's interface to dot-locking:
\dfnx{with-dot-lock} {file-name body \ldots} {value(s) of body}{syntax}
\begin{desc}
This procedure obtains the requested lock, and then calls
\ex{(\var{thunk})}. When \var{thunk} returns, the lock is released.
A non-local exit (\eg, throwing to a saved continuation or raising
an exception) also causes the lock to be released.
The procedure \ex{with-dot-lock*} obtains the requested lock, and
then calls \ex{(\var{thunk})}. When \var{thunk} returns, the lock is
released. A non-local exit (\eg, throwing to a saved continuation
or raising an exception) also causes the lock to be released.
After a normal return from \var{thunk}, its return values are
returned by \ex{with-dot-lock*}. The \ex{with-dot-lock} special