suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

clarification on closing pipe ports

Browse Source 
svn: r15903
This commit is contained in:
Matthew Flatt 2009-09-07 20:49:35 +00:00
parent bfe82b2f3d
commit a65ad71fad
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
collects/scribblings/reference/pipes.scrbl
View File

@ -14,8 +14,9 @@ between different processes.
Returns two port values: the first port is an input port and the Returns two port values: the first port is an input port and the
second is an output port. Data written to the output port is read from second is an output port. Data written to the output port is read from
the input port, with no intermediate buffering. The ports do not need the input port, with no intermediate buffering. Unlike some other
to be explicitly closed. kinds of ports, pipe ports do not need to be explicitly closed to be
reclaimed by @seclink["gc-model"]{garbage collection}.
If @scheme[limit] is @scheme[#f], the new pipe holds an unlimited If @scheme[limit] is @scheme[#f], the new pipe holds an unlimited
number of unread bytes (i.e., limited only by the available number of unread bytes (i.e., limited only by the available