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: Wed, 21 Sep 2011 02:48:41 +0200 [thread overview]
Message-ID: <874o06k9ee.fsf@ambire.localdomain> (raw)
In-Reply-To: <1316545329.28907.207.camel@homebase> (Paul Smith's message of "Tue, 20 Sep 2011 15:02:09 -0400")
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
() Paul Smith <psmith@gnu.org>
() Tue, 20 Sep 2011 15:02:09 -0400
I was thinking something like "gnu make" would be OK, but maybe there
are already conventions for applications/application-specific module
hierarchies that I should be following?
None that i am aware of. If the module is completely internal,
you can basically choose whatever pleases you. In the example
previously posted, i chose ‘(make-user)’ to ape '(guile-user)'.
BTW, appended is version 0.2. It fixes an infloop and flips the
logic from blacklist-plus-default-ok to whitelist-plus-default-wtf.
Too much fun...
[-- Attachment #2: procs-for-gnu-make-hacking.scm --]
[-- Type: application/x-scheme, Size: 1456 bytes --]
next prev parent reply other threads:[~2011-09-21 0:48 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
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 [this message]
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=874o06k9ee.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).