From c70f7d2ed213d413d9346a433da5d58081f03d61 Mon Sep 17 00:00:00 2001 From: Danny Yoo Date: Tue, 1 Jan 2013 00:48:50 -0800 Subject: [PATCH] Disambiguate sentence on custodian shutdown. See: http://lists.racket-lang.org/dev/archive/2012-December/011373.html Motivated by Sgeo's question in: http://racket-lang.org/irc-logs/20121229.txt at 22:10. --- collects/scribblings/reference/eval-model.scrbl | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/collects/scribblings/reference/eval-model.scrbl b/collects/scribblings/reference/eval-model.scrbl index 21287a7bac..6a190500ba 100644 --- a/collects/scribblings/reference/eval-model.scrbl +++ b/collects/scribblings/reference/eval-model.scrbl @@ -804,9 +804,9 @@ When a @tech{custodian} is shut down via @racket[custodian-shutdown-all], it forcibly and immediately closes the ports, TCP connections, @|etc|, that it manages, as well as terminating (or suspending) its threads. A custodian that has been -shut down cannot manage new objects. If the current custodian is shut -down before a procedure is called to create a managed resource (e.g., -@racket[open-input-port], @racket[thread]), the +shut down cannot manage new objects. After the current custodian is shut +down, if a procedure is called that attempts to create a managed resource (e.g., +@racket[open-input-port], @racket[thread]), then the @exnraise[exn:fail:contract]. A thread can have multiple managing custodians, and a suspended thread