mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-04-30 20:00:19 +02:00
Documentation fixes
* doc/ref/api-control: * doc/ref/compiler.texi: Language fixes * doc/ref/compiler ($kfun): Renamed argument clauses -> clause.
This commit is contained in:
parent
af1d55bcca
commit
a83de07e35
2 changed files with 9 additions and 9 deletions
|
@ -1699,7 +1699,7 @@ file descriptors), in Guile you can arrange to call a function while
|
||||||
binding a fluid to a particular value. That association between fluid
|
binding a fluid to a particular value. That association between fluid
|
||||||
and value will exist during the dynamic extent of the function call.
|
and value will exist during the dynamic extent of the function call.
|
||||||
|
|
||||||
Fluids are a therefore a building block for implementing dynamically
|
Fluids are therefore a building block for implementing dynamically
|
||||||
scoped variables. Dynamically scoped variables are useful when you want
|
scoped variables. Dynamically scoped variables are useful when you want
|
||||||
to set a variable to a value during some dynamic extent in the execution
|
to set a variable to a value during some dynamic extent in the execution
|
||||||
of your program and have them revert to their original value when the
|
of your program and have them revert to their original value when the
|
||||||
|
|
|
@ -9,7 +9,7 @@
|
||||||
|
|
||||||
Compilers! The word itself inspires excitement and awe, even among
|
Compilers! The word itself inspires excitement and awe, even among
|
||||||
experienced practitioners. But a compiler is just a program: an
|
experienced practitioners. But a compiler is just a program: an
|
||||||
eminently hackable thing. This section aims to to describe Guile's
|
eminently hackable thing. This section aims to describe Guile's
|
||||||
compiler in such a way that interested Scheme hackers can feel
|
compiler in such a way that interested Scheme hackers can feel
|
||||||
comfortable reading and extending it.
|
comfortable reading and extending it.
|
||||||
|
|
||||||
|
@ -200,11 +200,11 @@ expression from the same source language within the same module.
|
||||||
|
|
||||||
For example, you might compile the expression, @code{(define-module
|
For example, you might compile the expression, @code{(define-module
|
||||||
(foo))}. This will result in a Tree-IL expression and environment. But
|
(foo))}. This will result in a Tree-IL expression and environment. But
|
||||||
if you compiled a second expression, you would want to take into
|
if you compiled a second expression, you would want to take into account
|
||||||
account the compile-time effect of compiling the previous expression,
|
the compile-time effect of compiling the previous expression, which puts
|
||||||
which puts the user in the @code{(foo)} module. That is purpose of the
|
the user in the @code{(foo)} module. That is the purpose of the
|
||||||
``continuation environment''; you would pass it as the environment
|
``continuation environment''; you would pass it as the environment when
|
||||||
when compiling the subsequent expression.
|
compiling the subsequent expression.
|
||||||
|
|
||||||
For Scheme, an environment is a module. By default, the @code{compile}
|
For Scheme, an environment is a module. By default, the @code{compile}
|
||||||
and @code{compile-file} procedures compile in a fresh module, such
|
and @code{compile-file} procedures compile in a fresh module, such
|
||||||
|
@ -897,7 +897,7 @@ Note that all of these names with the exception of the @var{var}s in the
|
||||||
Additionally, there are three specific kinds of continuations that are
|
Additionally, there are three specific kinds of continuations that are
|
||||||
only used in function entries.
|
only used in function entries.
|
||||||
|
|
||||||
@deftp {CPS Continuation} $kfun src meta self tail clauses
|
@deftp {CPS Continuation} $kfun src meta self tail clause
|
||||||
Declare a function entry. @var{src} is the source information for the
|
Declare a function entry. @var{src} is the source information for the
|
||||||
procedure declaration, and @var{meta} is the metadata alist as described
|
procedure declaration, and @var{meta} is the metadata alist as described
|
||||||
above in Tree-IL's @code{<lambda>}. @var{self} is a variable bound to
|
above in Tree-IL's @code{<lambda>}. @var{self} is a variable bound to
|
||||||
|
@ -1043,7 +1043,7 @@ value associated with a given key, requiring that the key was present
|
||||||
already, and @code{intmap-remove}, which removes a key from an intmap.
|
already, and @code{intmap-remove}, which removes a key from an intmap.
|
||||||
|
|
||||||
Intmaps have a tree-like structure that is well-suited to set operations
|
Intmaps have a tree-like structure that is well-suited to set operations
|
||||||
such as union and intersection, so there is are also the binary
|
such as union and intersection, so there are also the binary
|
||||||
@code{intmap-union} and @code{intmap-intersect} procedures. If the
|
@code{intmap-union} and @code{intmap-intersect} procedures. If the
|
||||||
result is equivalent to either argument, that argument is returned
|
result is equivalent to either argument, that argument is returned
|
||||||
as-is; in that way, one can detect whether the set operation produced a
|
as-is; in that way, one can detect whether the set operation produced a
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue