From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: psmith@gnu.org
Cc: guile-user@gnu.org
Subject: Re: Using guile as an extension language for GNU make
Date: Mon, 19 Sep 2011 02:28:46 +0200 [thread overview]
Message-ID: <87sjntwf29.fsf@ambire.localdomain> (raw)
In-Reply-To: <1316374080.28907.163.camel@homebase> (Paul Smith's message of "Sun, 18 Sep 2011 15:28:00 -0400")
() Paul Smith <psmith@gnu.org>
() Sun, 18 Sep 2011 15:28:00 -0400
[new impl]
That's better than what I had before, but I still have some concerns.
For example, what if a Guile call wanted to return a list? I can use
display as above, but the list will be enclosed in parentheses, which is
not how make displays lists. Is there a clean way to handle this?
"Clean" in what way? Everything depends on what the expected (valid) use
of this facility would be. Could you give some examples (w/ failure cases)?
I could write a function then invoke it with scm_map() (right?) but this
seems like it might be work.
Everything is work. Even play is work (but hopefully more fun/interesting).
Also what if the data structure is more complex, where some elements of the
list are lists themselves, etc.? I can "flatten" the entire thing out, I
suppose.
Yes.
Or I could ignore them as above and require the Guile scripting to
convert the list into a string before returning it.
Right. The protocol is internal; you can choose 60/40 or 40/60.
I think concomitant w/ this particular hacking it would nice to implement
some of the make functions (e.g., ‘patsubst’) in Scheme. Enough of that
and you will end up {in,con}verting the "embedding" effort to an "extending"
effort as suggested by Ludo -- YHBW! :-D
next prev parent reply other threads:[~2011-09-19 0:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 0:10 Using guile as an extension language for GNU make Paul Smith
2011-09-18 12:10 ` Ludovic Courtès
2011-09-18 17:21 ` Embedding vs. Extending (was: Re: Using guile as an extension language for GNU make) Paul Smith
2011-09-18 21:48 ` Embedding vs. Extending Ludovic Courtès
2011-09-18 17:42 ` Using guile as an extension language for GNU make Paul Smith
2011-09-18 21:28 ` Ludovic Courtès
2011-09-18 15:30 ` Thien-Thi Nguyen
2011-09-18 19:28 ` Paul Smith
2011-09-19 0:28 ` Thien-Thi Nguyen [this message]
2011-09-19 15:14 ` Paul Smith
2011-09-19 19:41 ` Hans Aberg
2011-09-19 21:56 ` Paul Smith
2011-09-19 22:35 ` Hans Aberg
2011-09-19 23:00 ` Hans Aberg
2011-09-21 2:42 ` Mark H Weaver
2011-09-21 8:24 ` Hans Aberg
2011-09-20 16:17 ` Thien-Thi Nguyen
2011-09-20 17:31 ` Paul Smith
2011-09-20 19:02 ` Paul Smith
2011-09-21 0:48 ` Thien-Thi Nguyen
2011-09-20 20:39 ` Thien-Thi Nguyen
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=87sjntwf29.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=psmith@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).