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

Small guide fixes.

Browse Source 
Closes PR 15109.
This commit is contained in:
Vincent St-Amour 2016-01-01 12:51:20 -06:00
parent 8c8a76979b
commit 923b5864a5
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
pkgs/racket-doc/scribblings/guide/io.scrbl
View File

@ -69,10 +69,11 @@ file:
(close-output-port out)
]
Instead of having to match @racket[open-input-file] and
@racket[open-output-file] calls, most Racket programmers will instead
use @racket[call-with-output-file], which takes a function to call
with the output port; when the function returns, the port is closed.
Instead of having to match the open calls with close calls, most Racket
programmers will use the @racket[call-with-input-file] and
@racket[call-with-output-file] functions which take a function to call to carry
out the desired operation. This function gets as its only argument the port,
which is automatically opened and closed for the operation.
@examples[
#:eval io-eval
@ -318,7 +319,7 @@ Other structure types created by @racket[struct], which offer
more abstraction than @tech{prefab} structure types, normally
@racket[write] either using @racketresultfont{#<....>} notation (for
opaque structure types) or using @racketresultfont{#(....)} vector
notation (for transparent structure types). In neither can the
notation (for transparent structure types). In neither case can the
result be read back in as an instance of the structure type:
@interaction[