mirror/guile
mirror/guile
1
Fork 0
mirror of https://git.savannah.gnu.org/git/guile.git synced 2025-06-13 07:10:20 +02:00
Code Activity

* Updates for string- and vector-move-right/left! docstrings.

Browse source 
* Update Tcl war URLs.
This commit is contained in:
Neil Jerram 2001-11-18 22:10:41 +00:00
parent 3096b33f0d
commit 694a9bb34e
7 changed files with 64 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

18
doc/maint/guile.texi
View file

@ -4986,13 +4986,27 @@ returned by @code{vector-fill!} is unspecified.
vector-move-left! vector-move-left!
@deffn {Scheme Procedure} vector-move-left! vec1 start1 end1 vec2 start2 @deffn {Scheme Procedure} vector-move-left! vec1 start1 end1 vec2 start2
@deffnx {C Function} scm_vector_move_left_x (vec1, start1, end1, vec2, start2) @deffnx {C Function} scm_vector_move_left_x (vec1, start1, end1, vec2, start2)
Vector version of @code{substring-move-left!}. Copy elements from @var{vec1}, positions @var{start1} to @var{end1},
to @var{vec2} starting at position @var{start2}. @var{start1} and
@var{start2} are inclusive indices; @var{end1} is exclusive.
@code{vector-move-left!} copies elements in leftmost order.
Therefore, in the case where @var{vec1} and @var{vec2} refer to the
same vector, @code{vector-move-left!} is usually appropriate when
@var{start1} is greater than @var{start2}.
@end deffn @end deffn
vector-move-right! vector-move-right!
@deffn {Scheme Procedure} vector-move-right! vec1 start1 end1 vec2 start2 @deffn {Scheme Procedure} vector-move-right! vec1 start1 end1 vec2 start2
@deffnx {C Function} scm_vector_move_right_x (vec1, start1, end1, vec2, start2) @deffnx {C Function} scm_vector_move_right_x (vec1, start1, end1, vec2, start2)
Vector version of @code{substring-move-right!}. Copy elements from @var{vec1}, positions @var{start1} to @var{end1},
to @var{vec2} starting at position @var{start2}. @var{start1} and
@var{start2} are inclusive indices; @var{end1} is exclusive.
@code{vector-move-right!} copies elements in rightmost order.
Therefore, in the case where @var{vec1} and @var{vec2} refer to the
same vector, @code{vector-move-right!} is usually appropriate when
@var{start1} is less than @var{start2}.
@end deffn @end deffn
major-version major-version

5
doc/ref/ChangeLog
View file

@ -1,3 +1,8 @@
2001-11-18 Neil Jerram <neil@ossau.uklinux.net>
* scheme-data.texi (Vectors): Autoupdate docs for
vector-move-left! and vector-move-right!.
2001-11-16 Neil Jerram <neil@ossau.uklinux.net> 2001-11-16 Neil Jerram <neil@ossau.uklinux.net>
* debugging.texi, deprecated.texi, intro.texi, misc-modules.texi, * debugging.texi, deprecated.texi, intro.texi, misc-modules.texi,

18
doc/ref/scheme-data.texi
View file

@ -3515,12 +3515,26 @@ returned by @code{vector-fill!} is unspecified.
@deffn {Scheme Procedure} vector-move-left! vec1 start1 end1 vec2 start2 @deffn {Scheme Procedure} vector-move-left! vec1 start1 end1 vec2 start2
@deffnx {C Function} scm_vector_move_left_x (vec1, start1, end1, vec2, start2) @deffnx {C Function} scm_vector_move_left_x (vec1, start1, end1, vec2, start2)
Vector version of @code{substring-move-left!}. Copy elements from @var{vec1}, positions @var{start1} to @var{end1},
to @var{vec2} starting at position @var{start2}. @var{start1} and
@var{start2} are inclusive indices; @var{end1} is exclusive.
@code{vector-move-left!} copies elements in leftmost order.
Therefore, in the case where @var{vec1} and @var{vec2} refer to the
same vector, @code{vector-move-left!} is usually appropriate when
@var{start1} is greater than @var{start2}.
@end deffn @end deffn
@deffn {Scheme Procedure} vector-move-right! vec1 start1 end1 vec2 start2 @deffn {Scheme Procedure} vector-move-right! vec1 start1 end1 vec2 start2
@deffnx {C Function} scm_vector_move_right_x (vec1, start1, end1, vec2, start2) @deffnx {C Function} scm_vector_move_right_x (vec1, start1, end1, vec2, start2)
Vector version of @code{substring-move-right!}. Copy elements from @var{vec1}, positions @var{start1} to @var{end1},
to @var{vec2} starting at position @var{start2}. @var{start1} and
@var{start2} are inclusive indices; @var{end1} is exclusive.
@code{vector-move-right!} copies elements in rightmost order.
Therefore, in the case where @var{vec1} and @var{vec2} refer to the
same vector, @code{vector-move-right!} is usually appropriate when
@var{start1} is less than @var{start2}.
@end deffn @end deffn
@subsection Vector Selection @subsection Vector Selection

5
doc/tutorial/ChangeLog
View file

@ -1,3 +1,8 @@
2001-11-18 Neil Jerram <neil@ossau.uklinux.net>
* guile-tut.texi (History of Guile and its motivations): Update
Tcl war URLs.
2001-09-19 Thien-Thi Nguyen <ttn@glug.org> 2001-09-19 Thien-Thi Nguyen <ttn@glug.org>
* guile-tut.texi: Fix improper `@result' usage. * guile-tut.texi: Fix improper `@result' usage.

4
doc/tutorial/guile-tut.texi
View file

@ -285,7 +285,7 @@ In the fall of 1994, Richard Stallman, director of the GNU project,
posted an article with the subject "Why you should not use Tcl", in posted an article with the subject "Why you should not use Tcl", in
which he argued that Tcl is inadequate as an extension language. This which he argued that Tcl is inadequate as an extension language. This
generated a flurry of flames (available in the hypermail archive generated a flurry of flames (available in the hypermail archive
(@url{http://www.utdallas.edu/acc/glv/Tcl/war/}) @strong{The Tcl War}). (@url{http://www.vanderburg.org/Tcl/war/}) @strong{The Tcl War}).
@cindex Stallman, Richard @cindex Stallman, Richard
@cindex GNU project @cindex GNU project
@cindex Tcl @cindex Tcl
@ -293,7 +293,7 @@ generated a flurry of flames (available in the hypermail archive
The result was that Stallman then proposed his design for the GNU The result was that Stallman then proposed his design for the GNU
Extension Language, first called GEL and then renamed Guile. The Extension Language, first called GEL and then renamed Guile. The
discussion triggered by that article is also available in a hypermail discussion triggered by that article is also available in a hypermail
archive, @url{http://www.utdallas.edu/acc/glv/Tcl/war2/}. archive, @url{http://www.vanderburg.org/Tcl/war2/}.
One interesting feature of this GNU Extension Language plan was that One interesting feature of this GNU Extension Language plan was that
users should have a @emph{choice} of languages to use in extending their users should have a @emph{choice} of languages to use in extending their

6
libguile/ChangeLog
View file

@ -1,3 +1,9 @@
2001-11-18 Neil Jerram <neil@ossau.uklinux.net>
* vectors.c (scm_vector_move_left_x, scm_vector_move_right_x):
Rewrite docstrings without reference to substring-move-left/right,
since the latter no longer exist.
2001-11-17 Dirk Herrmann <D.Herrmann@tu-bs.de> 2001-11-17 Dirk Herrmann <D.Herrmann@tu-bs.de>
* eval.c: Removed bogus comment about acros. * eval.c: Removed bogus comment about acros.

16
libguile/vectors.c
View file

@ -275,7 +275,13 @@ scm_vector_equal_p(SCM x, SCM y)
SCM_DEFINE (scm_vector_move_left_x, "vector-move-left!", 5, 0, 0, SCM_DEFINE (scm_vector_move_left_x, "vector-move-left!", 5, 0, 0,
(SCM vec1, SCM start1, SCM end1, SCM vec2, SCM start2), (SCM vec1, SCM start1, SCM end1, SCM vec2, SCM start2),
"Vector version of @code{substring-move-left!}.") "Copy elements from @var{vec1}, positions @var{start1} to @var{end1},\n"
"to @var{vec2} starting at position @var{start2}. @var{start1} and\n"
"@var{start2} are inclusive indices; @var{end1} is exclusive.\n\n"
"@code{vector-move-left!} copies elements in leftmost order.\n"
"Therefore, in the case where @var{vec1} and @var{vec2} refer to the\n"
"same vector, @code{vector-move-left!} is usually appropriate when\n"
"@var{start1} is greater than @var{start2}.")
#define FUNC_NAME s_scm_vector_move_left_x #define FUNC_NAME s_scm_vector_move_left_x
{ {
long i; long i;
@ -298,7 +304,13 @@ SCM_DEFINE (scm_vector_move_left_x, "vector-move-left!", 5, 0, 0,
SCM_DEFINE (scm_vector_move_right_x, "vector-move-right!", 5, 0, 0, SCM_DEFINE (scm_vector_move_right_x, "vector-move-right!", 5, 0, 0,
(SCM vec1, SCM start1, SCM end1, SCM vec2, SCM start2), (SCM vec1, SCM start1, SCM end1, SCM vec2, SCM start2),
"Vector version of @code{substring-move-right!}.") "Copy elements from @var{vec1}, positions @var{start1} to @var{end1},\n"
"to @var{vec2} starting at position @var{start2}. @var{start1} and\n"
"@var{start2} are inclusive indices; @var{end1} is exclusive.\n\n"
"@code{vector-move-right!} copies elements in rightmost order.\n"
"Therefore, in the case where @var{vec1} and @var{vec2} refer to the\n"
"same vector, @code{vector-move-right!} is usually appropriate when\n"
"@var{start1} is less than @var{start2}.")
#define FUNC_NAME s_scm_vector_move_right_x #define FUNC_NAME s_scm_vector_move_right_x
{ {
long i; long i;