[Guile-commits] GNU Guile branch, master, updated. release_1-9-6-10-g3733df0

[Neil Jerram]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU Guile".

http://git.savannah.gnu.org/cgit/guile.git/commit/?id=3733df073f5b0cca088b779a26a71a4618ececcb

The branch, master has been updated
       via  3733df073f5b0cca088b779a26a71a4618ececcb (commit)
       via  2c18ac5f8e89580c44596d9c7b8a870da26c8b24 (commit)
      from  6751d6db6bdf3303b82dd184249e570930a6c561 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 3733df073f5b0cca088b779a26a71a4618ececcb
Author: Neil Jerram <address@hidden>
Date:   Fri Dec 18 01:11:40 2009 +0000

    Update and simplify statement about RnRS support
    
    * doc/ref/scheme-intro.texi (Guile Scheme): Mention R6RS as well as
      R5RS.  Simplify text.

commit 2c18ac5f8e89580c44596d9c7b8a870da26c8b24
Author: Brian Gough <address@hidden>
Date:   Tue Dec 15 10:28:49 2009 +0000

    make the use of the 5-argument @xref command consistent
    
    A few of the @xref references to external manuals in the documentation
    are using an old 4-argument form that produces an undefined reference
    in the printed manual.  The following patch makes them consistent with
    the 5-argument @xrefs used elsewhere in the manual.
    
    --
    Brian Gough
    
    Network Theory Ltd,
    Publishing Free Software Manuals --- http://www.network-theory.co.uk/
    
    >From 6ca0417830dc5a98699a15808591dc1f2a90dfac Mon Sep 17 00:00:00 2001
    From: Brian Gough <address@hidden>
    Date: Mon, 14 Dec 2009 21:34:59 +0000
    Subject: [PATCH] make the use of the 5-argument @xref command consistent
     when referring to other manuals.

-----------------------------------------------------------------------

Summary of changes:
 doc/ref/autoconf.texi     |   17 +++++++++--------
 doc/ref/scheme-ideas.texi |    7 ++++---
 doc/ref/scheme-intro.texi |   13 +++++--------
 3 files changed, 18 insertions(+), 19 deletions(-)

diff --git a/doc/ref/autoconf.texi b/doc/ref/autoconf.texi
index ae807c2..1e334c0 100644
--- a/doc/ref/autoconf.texi
+++ b/doc/ref/autoconf.texi
@@ -11,7 +11,6 @@
 When Guile is installed, a pkg-config description file and a set of
 Autoconf macros is installed.  This chapter documents pkg-config and
 Autoconf support, as well as the high-level guile-tool Autofrisk.
address@hidden,The GNU Autoconf Manual,,autoconf}, for more info.
 
 @menu
 * Autoconf Background::         Why use autoconf?
@@ -25,19 +24,21 @@ Autoconf support, as well as the high-level guile-tool 
Autofrisk.
 @node Autoconf Background
 @section Autoconf Background
 
-As explained elsewhere (@pxref{Top,The GNU Autoconf Manual,,autoconf}), any
-package needs configuration at build-time.  If your package uses Guile (or
-uses a package that in turn uses Guile), you probably need to know what
-specific Guile features are available and details about them.
+As explained in the @cite{GNU Autoconf Manual}, any package needs
+configuration at build-time (@pxref{Top, ,Introduction,autoconf,The GNU
+Autoconf Manual}).  If your package uses Guile (or uses a package that
+in turn uses Guile), you probably need to know what specific Guile
+features are available and details about them.
 
 The way to do this is to write feature tests and arrange for their execution
 by the @file{configure} script, typically by adding the tests to
 @file{configure.ac}, and running @code{autoconf} to create @file{configure}.
 Users of your package then run @file{configure} in the normal way.
 
-Macros are a way to make common feature tests easy to express.  Autoconf
-provides a wide range of macros (@pxref{Existing Tests,,,autoconf}), and
-Guile installation provides Guile-specific tests in the areas of:
+Macros are a way to make common feature tests easy to express.
+Autoconf provides a wide range of macros 
+(@pxref{Existing Tests,,,autoconf,The GNU Autoconf Manual}), 
+and Guile installation provides Guile-specific tests in the areas of:
 program detection, compilation flags reporting, and Scheme module
 checks.
 
diff --git a/doc/ref/scheme-ideas.texi b/doc/ref/scheme-ideas.texi
index 55093cf..e9b7765 100644
--- a/doc/ref/scheme-ideas.texi
+++ b/doc/ref/scheme-ideas.texi
@@ -549,9 +549,10 @@ and then by describing the value and side effects of 
evaluation for each
 type of expression individually.
 
 @noindent
-So, address@hidden definitions are approximate.  For the whole and
-detailed truth, see @xref{Formal syntax and semantics,R5RS
-syntax,,r5rs}.} address@hidden
+So, address@hidden definitions are approximate.  For the whole
+and detailed truth, see @ref{Formal syntax and semantics,R5RS
+syntax,,r5rs,The Revised(5) Report on the Algorithmic Language
+Scheme}.} address@hidden
 
 @itemize @bullet
 
diff --git a/doc/ref/scheme-intro.texi b/doc/ref/scheme-intro.texi
index e3542d8..57aa18f 100644
--- a/doc/ref/scheme-intro.texi
+++ b/doc/ref/scheme-intro.texi
@@ -15,14 +15,11 @@ series of reports known as @dfn{RnRS}.  @dfn{RnRS} is 
shorthand for the
 @ifnottex
 @dfn{Revised^n Report on the Algorithmic Language Scheme}.
 @end ifnottex
-The current latest revision of RnRS is version 5
-(@pxref{Top,R5RS,,r5rs}), and Guile 1.4 is fully compliant with the
-Scheme specification in this revision.
-
-But Guile, like most Scheme implementations, also goes beyond R5RS in
-many ways, because R5RS does not give specifications (or even
-recommendations) regarding many issues that are important in practical
-programming.  Some of the areas where Guile extends R5RS are:
+Guile complies fully with R5RS (@pxref{Top,
+,Introduction,r5rs,R5RS}), and implements some aspects of R6RS.
+
+Guile also has many extensions that go beyond these reports.  Some of
+the areas where Guile extends R5RS are:
 
 @itemize @bullet
 @item


hooks/post-receive
-- 
GNU Guile