From: Paul Smith <psmith@gnu.org>
To: Kirill Smelkov <kirr@navytux.spb.ru>
Cc: Guile Users <guile-user@gnu.org>,
make-alpha@gnu.org, Thien-Thi Nguyen <ttn@gnuvola.org>
Subject: Re: Guile support in GNU make
Date: Tue, 31 Jan 2012 16:32:06 -0500 [thread overview]
Message-ID: <1328045526.4002.17.camel@psmith-ubeta> (raw)
In-Reply-To: <20120131191756.GB8415@mini.zxlink>
On Tue, 2012-01-31 at 23:17 +0400, Kirill Smelkov wrote:
> from Debian testing, and I don't see the problem for test from the
> make.info example - it works ok:
>
> define GUILEIO
> (define (mkclose)
> (close-port MKPORT)
> #f)
>
> #f
> endef
>
> Is it that (define ...) or maybe I've misunderstood something?
It's because of the final "#f" in the define GUILEIO. That means that
the final result of passing that content to Guile is #f, rather than the
result of evaluating the final (define ...).
If you remove that trailing "#f", or use one of the other examples we've
bandied about, you'll see the same behavior (with the older version,
before I fixed it).
Cheers!
next prev parent reply other threads:[~2012-01-31 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1316557011.28907.237.camel@homebase>
[not found] ` <1326572016.3482.144.camel@homebase>
[not found] ` <20120122182923.GB3460@mini.zxlink>
2012-01-22 21:56 ` Guile support in GNU make Paul Smith
2012-01-23 6:01 ` Thien-Thi Nguyen
2012-01-23 6:08 ` Thien-Thi Nguyen
2012-01-29 20:05 ` Paul Smith
2012-01-31 19:17 ` Kirill Smelkov
2012-01-31 21:32 ` Paul Smith [this message]
2012-01-25 23:45 ` Ludovic Courtès
2012-01-14 19:55 Paul Smith
2012-01-15 8:51 ` Thien-Thi Nguyen
2012-01-15 12:33 ` Thien-Thi Nguyen
2012-01-15 16:12 ` Paul Smith
2012-01-15 20:11 ` Thien-Thi Nguyen
2012-01-15 20:49 ` Paul Smith
2012-01-15 22:02 ` Ludovic Courtès
2012-01-16 14:07 ` Paul Smith
2012-01-17 22:42 ` Ludovic Courtès
2012-01-17 23:26 ` Paul Smith
2012-01-19 20:42 ` Ludovic Courtès
2012-01-19 22:14 ` 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=1328045526.4002.17.camel@psmith-ubeta \
--to=psmith@gnu.org \
--cc=guile-user@gnu.org \
--cc=kirr@navytux.spb.ru \
--cc=make-alpha@gnu.org \
--cc=ttn@gnuvola.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).