Updates for load-extension et al.

[bpt/guile.git] / doc / gh.texi

diff --git a/doc/gh.texi b/doc/gh.texi
index 691fd55..668270c 100644 (file)
--- a/doc/gh.texi
+++ b/doc/gh.texi
@@ -244,12 +244,12 @@ parentheses, you must either concatenate them into one string, or use
 @deftypefun SCM gh_eval_file (char *@var{fname})
 @deftypefunx SCM gh_load (char *@var{fname})
 @code{gh_eval_file} is completely analogous to @code{gh_eval_str()},
-except that a whole file is evaluated instead of a string.  Returns the
-result of the last expression evaluated.
+except that a whole file is evaluated instead of a string.
+@code{gh_eval_file} returns @code{SCM_UNSPECIFIED}.
 
 @code{gh_load} is identical to @code{gh_eval_file} (it's a macro that
 calls @code{gh_eval_file} on its argument).  It is provided to start
-making the @code{gh_} interface match the R4RS Scheme procedures
+making the @code{gh_} interface match the R5RS Scheme procedures
 closely.
 @end deftypefun
 
@@ -568,8 +568,8 @@ interface; they take and return objects of type SCM, and one could
 basically use them to write C code that mimics Scheme code.
 
 I will list these routines here without much explanation, since what
-they do is the same as documented in @ref{Standard Procedures, R4RS, ,
-r4rs, R4RS}.  But I will point out that when a procedure takes a
+they do is the same as documented in @ref{Standard procedures, R5RS, ,
+r5rs, R5RS}.  But I will point out that when a procedure takes a
 variable number of arguments (such as @code{gh_list}), you should pass
 the constant @var{SCM_EOL} from C to signify the end of the list.