[Guile-commits] GNU Guile branch, stable-2.0, updated. v2.0.0-52-gfba502d

[Ludovic Courtès]

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=fba502dbccfa57c6a8f5b7bffa4fddfb22725677

The branch, stable-2.0 has been updated
       via  fba502dbccfa57c6a8f5b7bffa4fddfb22725677 (commit)
      from  bd79ebf3188ad0dc9f45290112f603f33af86f88 (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 fba502dbccfa57c6a8f5b7bffa4fddfb22725677
Author: Ludovic Courtès <address@hidden>
Date:   Wed Mar 2 22:12:56 2011 +0100

    Improve the documentation for `dynamic-link'.
    
    * doc/ref/api-foreign.texi (Foreign Libraries): Make it clear that the
      LIBRARY argument of `dynamic-link' should not contain an extension.
      (Foreign Functions): Add cross-reference from `load-extension' to
      `dynamic-link'.  Typeset file names and module names correctly.

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

Summary of changes:
 doc/ref/api-foreign.texi |   13 ++++++++++---
 1 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/doc/ref/api-foreign.texi b/doc/ref/api-foreign.texi
index e9d7df6..b91439e 100644
--- a/doc/ref/api-foreign.texi
+++ b/doc/ref/api-foreign.texi
@@ -79,6 +79,12 @@ Normally, @var{library} is just the name of some shared 
library file
 that will be searched for in the places where shared libraries usually
 reside, such as in @file{/usr/lib} and @file{/usr/local/lib}.
 
address@hidden should not contain an extension such as @code{.so}.  The
+correct file name extension for the host operating system is provided
+automatically, according to libltdl's rules (@pxref{Libltdl interface,
+lt_dlopenext, @code{lt_dlopenext}, libtool, Shared Library Support for
+GNU}).
+
 When @var{library} is omitted, a @dfn{global symbol handle} is returned.  This
 handle provides access to the symbols available to the program at run-time,
 including those exported by the program itself and the shared libraries already
@@ -196,12 +202,13 @@ In that case, you would statically link your program with 
the desired
 library, and register its init function right after Guile has been
 initialized.
 
-LIB should be a string denoting a shared library without any file type
-suffix such as ".so".  The suffix is provided automatically.  It
+As for @code{dynamic-link}, @var{lib} should not contain any suffix such
+as @code{.so} (@pxref{Foreign Libraries, dynamic-link}).  It
 should also not contain any directory components.  Libraries that
 implement Guile Extensions should be put into the normal locations for
 shared libraries.  We recommend to use the naming convention
-libguile-bla-blum for a extension related to a module `(bla blum)'.
address@hidden for a extension related to a module @code{(bla
+blum)}.
 
 The normal way for a extension to be used is to write a small Scheme
 file that defines a module, and to load the extension into this


hooks/post-receive
-- 
GNU Guile