From: BT Templeton <bpt@hcoop.net>
To: guile-devel@gnu.org
Subject: language environments
Date: Sat, 09 Jul 2011 16:30:56 -0400 [thread overview]
Message-ID: <87wrfrqjr3.fsf@olor.terpri.org> (raw)
How are language environments (i.e., the values passed as `#:env'
arguments to the various compilation functions) supposed to be used?
Currently all languages use it as the value of the current module, but
would it be appropriate to use the environment value to keep track of
other compilation-unit-specific settings like the default binding mode
for Elisp or global declarations for CL?
--
Inteligenta persono lernas la lingvon Esperanton rapide kaj facile.
Esperanto estas moderna, kultura lingvo por la mondo. Simpla, fleksebla,
belsona, Esperanto estas la praktika solvo de la problemo de universala
interkompreno. Lernu la interlingvon Esperanton! http://lernu.net/
next reply other threads:[~2011-07-09 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 20:30 BT Templeton [this message]
2011-07-11 9:57 ` language environments Andy Wingo
2011-07-12 2:53 ` BT Templeton
2011-12-06 10:20 ` Andy Wingo
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=87wrfrqjr3.fsf@olor.terpri.org \
--to=bpt@hcoop.net \
--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).