From: arne_bab@web.de
To: guile-devel@gnu.org
Cc: arne_bab@web.de
Subject: [PATCH] doc: describe the -e (module) shorthand as on equal footing with (@ ...)
Date: Wed, 18 May 2016 22:25:07 +0200 [thread overview]
Message-ID: <e5938da9b89fcee19364.1463603107@fluss.Baez> (raw)
doc/ref/guile-invoke.texi | 15 ++++------
doc/ref/scheme-scripts.texi | 62 +++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 68 insertions(+), 9 deletions(-)
# HG changeset patch
# User Arne Babenhauserheide <arne.babenhauserheide@kit.edu>
# Date 1463602731 -7200
# Wed May 18 22:18:51 2016 +0200
# Node ID e5938da9b89fcee1936487df32fb649135d8a94c
# Parent 4f269918e38cd48905546c485173c4f9dbfa0717
doc: describe the -e (module) shorthand as on equal footing with (@ ...)
diff --git a/doc/ref/guile-invoke.texi b/doc/ref/guile-invoke.texi
--- a/doc/ref/guile-invoke.texi
+++ b/doc/ref/guile-invoke.texi
@@ -102,15 +102,12 @@ that is defined in the script. It can a
@var{module-name} @var{symbol})}, and in that case, the symbol is
looked up in the module named @var{module-name}.
-For compatibility with some versions of Guile 1.4, you can also use the
-form @code{(symbol ...)} (that is, a list of only symbols that doesn't
-start with @code{@@}), which is equivalent to @code{(@@ (symbol ...)
-main)}, or @code{(symbol ...) symbol} (that is, a list of only symbols
-followed by a symbol), which is equivalent to @code{(@@ (symbol ...)
-symbol)}. We recommend to use the equivalent forms directly since they
-correspond to the @code{(@@ ...)} read syntax that can be used in
-normal code. See @ref{Using Guile Modules} and @ref{Scripting
-Examples}.
+As a shorthand you can use the form @code{(symbol ...)}, that is, a
+list of only symbols that doesn't start with @code{@@}. It is
+equivalent to @code{(@@ @var{module-name} main)} with @code{(symbol ...)}
+the @var{module-name}. To use a different function than @var{main},
+you can use the form @code{(symbol ...) function}. See @ref{Using
+Guile Modules} and @ref{Scripting Examples}.
@item -ds
Treat a final @option{-s} option as if it occurred at this point in the
diff --git a/doc/ref/scheme-scripts.texi b/doc/ref/scheme-scripts.texi
--- a/doc/ref/scheme-scripts.texi
+++ b/doc/ref/scheme-scripts.texi
@@ -293,6 +293,11 @@ and exit.
Load the file @file{/u/jimb/ex4}, and then call the function
@code{main}, passing it the list @code{("/u/jimb/ex4" "foo")}.
+@item guile -e '(ex4)' -s /u/jimb/ex4.scm foo
+Load the file @file{/u/jimb/ex4.scm}, and then call the function
+@code{main} from the module '(ex4)', passing it the list
+@code{("/u/jimb/ex4" "foo")}.
+
@item guile -l first -ds -l last -s script
Load the files @file{first}, @file{script}, and @file{last}, in that
order. The @code{-ds} switch says when to process the @code{-s}
@@ -402,6 +407,63 @@ 1
100891344545564193334812497256
@end example
+To execute the function main from a module, we can use the special form
+@code{(@@ (module) function)}:
+@example
+#!/usr/local/bin/guile \
+-l fact -e (@@ (fac) main) -s
+!#
+(define-module (fac)
+ #:export (main))
+
+(define (choose n m)
+ (/ (fact m) (* (fact (- m n)) (fact n))))
+
+(define (main args)
+ (let ((n (string->number (cadr args)))
+ (m (string->number (caddr args))))
+ (display (choose n m))
+ (newline)))
+@end example
+
+We can use @code{@@@@} to run non-exported functions. For exported
+functions, we can simplify this call with the shorthand @code{(module)}:
+@example
+#!/usr/local/bin/guile \
+-l fact -e (fac) -s
+!#
+(define-module (fac)
+ #:export (main))
+
+(define (choose n m)
+ (/ (fact m) (* (fact (- m n)) (fact n))))
+
+(define (main args)
+ (let ((n (string->number (cadr args)))
+ (m (string->number (caddr args))))
+ (display (choose n m))
+ (newline)))
+@end example
+
+For maximum portability among *nixes, we can use the shell to
+@code{exec} guile with specified command line arguments. Here we need to
+take care to quote the command arguments correctly:
+@example
+#!/usr/bin env sh
+exec guile -l fact -e '(@@ (fac) main)' -s "$0" "$@"
+!#
+(define-module (fac)
+ #:export (main))
+
+(define (choose n m)
+ (/ (fact m) (* (fact (- m n)) (fact n))))
+
+(define (main args)
+ (let ((n (string->number (cadr args)))
+ (m (string->number (caddr args))))
+ (display (choose n m))
+ (newline)))
+@end example
@c Local Variables:
@c TeX-master: "guile.texi"
next reply other threads:[~2016-05-18 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 20:25 arne_bab [this message]
2016-06-26 21:21 ` [PATCH] doc: describe the -e (module) shorthand as on equal footing with (@ ...) Arne Babenhauserheide
2016-06-27 8:08 ` Andy Wingo
2016-07-06 21:14 ` Arne Babenhauserheide
2016-07-07 10:19 ` Andy Wingo
2016-09-29 15:14 ` Arne Babenhauserheide
2016-12-04 23:18 ` Arne Babenhauserheide
2017-02-07 14:16 ` Arne Babenhauserheide
2017-02-13 21:03 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5938da9b89fcee19364.1463603107@fluss.Baez \
--to=arne_bab@web.de \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).