[Guile-commits] branch main updated: Review REFFIXME

[Daniel Llorens]

This is an automated email from the git hooks/post-receive script.

lloda pushed a commit to branch main
in repository guile.

The following commit(s) were added to refs/heads/main by this push:
     new dc7f1b4  Review REFFIXME
dc7f1b4 is described below

commit dc7f1b403b536a0ddd5acdef468b7cf0331ac531
Author: Daniel Llorens <lloda@sarc.name>
AuthorDate: Mon Dec 13 08:11:29 2021 +0100

    Review REFFIXME
    
    H/t t20kdc on #guile.
---
 doc/ref/api-procedures.texi   |  4 ++--
 doc/ref/api-utility.texi      |  5 +++--
 doc/ref/libguile-program.texi | 10 +++++++---
 3 files changed, 12 insertions(+), 7 deletions(-)

diff --git a/doc/ref/api-procedures.texi b/doc/ref/api-procedures.texi
index 8c53369..27489d9 100644
--- a/doc/ref/api-procedures.texi
+++ b/doc/ref/api-procedures.texi
@@ -801,8 +801,8 @@ procedure has a so-called @dfn{setter} attached, which is a 
procedure
 for storing something into a data structure.
 
 Procedures with setters are treated specially when the procedure appears
-in the special form @code{set!} (REFFIXME).  How it works is best shown
-by example.
+in the special form @code{set!}. @c (REFFIXME)
+How it works is best shown by example.
 
 Suppose we have a procedure called @code{foo-ref}, which accepts two
 arguments, a value of type @code{foo} and an integer.  The procedure
diff --git a/doc/ref/api-utility.texi b/doc/ref/api-utility.texi
index 5c01429..cb7e32f 100644
--- a/doc/ref/api-utility.texi
+++ b/doc/ref/api-utility.texi
@@ -184,8 +184,9 @@ properties allow you to do just that.
 
 Guile's representation of an object property is a procedure-with-setter
 (@pxref{Procedures with Setters}) that can be used with the generalized
-form of @code{set!} (REFFIXME) to set and retrieve that property for any
-Scheme object.  So, setting a property looks like this:
+form of @code{set!} @c (REFFIXME)
+to set and retrieve that property for any Scheme object.  So, setting a
+property looks like this:
 
 @lisp
 (set! (my-property obj1) value-for-obj1)
diff --git a/doc/ref/libguile-program.texi b/doc/ref/libguile-program.texi
index 3b74083..435c26c 100644
--- a/doc/ref/libguile-program.texi
+++ b/doc/ref/libguile-program.texi
@@ -610,8 +610,7 @@ The C level work required in this model usually consists of 
packaging
 and exporting functions and application objects such that they can be
 seen and manipulated on the Scheme level.  To help with this, Guile's C
 language interface includes utility features that aim to make this kind
-of integration very easy for the application developer.  These features
-are documented later in this part of the manual: see REFFIXME.
+of integration very easy for the application developer.
 
 This model, though, is really just one of a range of possible
 programming options.  If all of the functionality that you need is
@@ -704,20 +703,25 @@ written, most of the difficulties of memory management 
can be avoided by
 using Guile's C interface features from the start.
 
 For the full documentation on writing C code for Guile and connecting
-existing C code to the Guile world, see REFFIXME.
+existing C code to the Guile world, see @ref{Defining New
+Foreign Object Types}, @ref{Primitive Procedures}, and @ref{Foreign
+Function Interface}.
 
 
 @node Basic Constraints
 @subsubsection Functional and Performance Constraints
 
+@c REFFIXME
 
 @node Style Choices
 @subsubsection Your Preferred Programming Style
 
+@c REFFIXME
 
 @node Program Control
 @subsubsection What Controls Program Execution?
 
+@c REFFIXME
 
 @node User Programming
 @subsection How About Application Users?