guix/guix
3
5
Fork 0
mirror of git://git.savannah.gnu.org/guix.git synced 2023-12-14 03:33:07 +01:00
Code Issues Releases Wiki Activity

doc: cookbook: Mention "#true" and "#false".

Browse source 
* doc/guix-cookbook.texi (A Scheme Crash Course): Mention "#true" and
"#false".
(Extended example): Likewise.
This commit is contained in:
Ludovic Courtès 2020-10-14 11:28:30 +02:00
parent 028119e9f5
commit cd958802f2
No known key found for this signature in database
GPG key ID: 090B11993D9AEBB5
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/guix-cookbook.texi
View file

@ -128,8 +128,9 @@ REPL.
@item @item
Scheme syntax boils down to a tree of expressions (or @emph{s-expression} in Scheme syntax boils down to a tree of expressions (or @emph{s-expression} in
Lisp lingo). An expression can be a literal such as numbers and strings, or a Lisp lingo). An expression can be a literal such as numbers and strings, or a
compound which is a parenthesized list of compounds and literals. @code{#t} compound which is a parenthesized list of compounds and literals. @code{#true}
and @code{#f} stand for the Booleans ``true'' and ``false'', respectively. and @code{#false} (abbreviated @code{#t} and @code{#f}) stand for the
Booleans ``true'' and ``false'', respectively.
Examples of valid expressions: Examples of valid expressions:
@ -1090,9 +1091,9 @@ this:
#t) #t)
@end lisp @end lisp
The procedure must return @code{#t} on success. It's brittle to rely on the return The procedure must return @code{#true} on success. It's brittle to rely on the return
value of the last expression used to tweak the phase because there is no value of the last expression used to tweak the phase because there is no
guarantee it would be a @code{#t}. Hence the trailing @code{#t} to ensure the right value guarantee it would be a @code{#true}. Hence the trailing @code{#true} to ensure the right value
is returned on success. is returned on success.
@subsubsection Code staging @subsubsection Code staging