mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-06-18 17:50:29 +02:00
* configure.in: Use AC_PROG_LIBTOOL instead of AM_PROG_LIBTOOL.
* scheme-compound.texi (Hash Table Reference): Renamed hash-map --> hash-map->list. * configure.in: Use AC_PROG_LIBTOOL instead of AM_PROG_LIBTOOL.
This commit is contained in:
parent
344a212fd1
commit
c78a96e063
6 changed files with 20 additions and 7 deletions
|
@ -1,3 +1,8 @@
|
|||
2004-02-15 Mikael Djurfeldt <mdj@chunk.mit.edu>
|
||||
|
||||
* scheme-compound.texi (Hash Table Reference): Renamed hash-map
|
||||
--> hash-map->list.
|
||||
|
||||
2004-02-15 Kevin Ryde <user42@zip.com.au>
|
||||
|
||||
* scheme-compound.texi (Hash Table Reference): In scm_hash_ref etc,
|
||||
|
|
|
@ -2481,17 +2481,17 @@ create an entry for it with @var{init} as the value, and return that
|
|||
pair.
|
||||
@end deffn
|
||||
|
||||
@deffn {Scheme Procedure} hash-map proc table
|
||||
@deffn {Scheme Procedure} hash-map->list proc table
|
||||
@deffnx {Scheme Procedure} hash-for-each proc table
|
||||
@deffnx {C Function} scm_hash_map (proc, table)
|
||||
@deffnx {C Function} scm_hash_map_to_list (proc, table)
|
||||
@deffnx {C Function} scm_hash_for_each (proc, table)
|
||||
Apply @var{proc} to the entries in the given hash @var{table}. Each
|
||||
call is @code{(@var{proc} @var{key} @var{value})}. @code{hash-map}
|
||||
call is @code{(@var{proc} @var{key} @var{value})}. @code{hash-map->list}
|
||||
returns a list of the results from these calls, @code{hash-for-each}
|
||||
discards the results and returns an unspecified value.
|
||||
|
||||
Calls are made over the table entries in an unspecified order, and for
|
||||
@code{hash-map} the order of the values in the returned list is
|
||||
@code{hash-map->list} the order of the values in the returned list is
|
||||
unspecified. Results will be unpredictable if @var{table} is modified
|
||||
while iterating.
|
||||
|
||||
|
@ -2499,7 +2499,7 @@ For example the following returns a new alist comprising all the
|
|||
entries from @code{mytable}, in no particular order.
|
||||
|
||||
@example
|
||||
(hash-map cons mytable)
|
||||
(hash-map->list cons mytable)
|
||||
@end example
|
||||
@end deffn
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue