From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Keith Wright <kwright@keithdiane.us>
Cc: guile-user@gnu.org
Subject: Re: rfc (define-module ... #:use-modules ...)
Date: Sun, 07 Oct 2007 11:37:04 +0200 [thread overview]
Message-ID: <87hcl36zb3.fsf@ambire.localdomain> (raw)
In-Reply-To: <200710070405.l9745DBe003737@fcs13.keithdiane.us> (Keith Wright's message of "Sun\, 7 Oct 2007 00\:05\:13 -0400")
[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]
() Keith Wright <kwright@keithdiane.us>
() Sun, 7 Oct 2007 00:05:13 -0400
Consensus - same sense or feeling (<-Latin sentire)
Concensus - if that were a word,
it might mean same head-count
thanks; i stand corrected.
Anyway carry on. Or muddle on. My opinion means
little with no code to back it up, and I have none.
i appreciate when anyone shares their opinion because
it gives me (some) insight into other points of view.
code is opinions petrified and sometimes worth less.
Are you worried about the systactic difference
between [...] ?
yes, precisely.
The later (with parentheses on both sides)
seems more lispy to me, but it seems like a
pretty trivial change of syntax. It would
be more interesting to learn about the deep
magick hidden in the blah blah.
IIUC, first blah in r6rs is `(export EXPORT-SPEC...)'.
second blah is `(import IMPORT-SPEC...)'.
I would leave modules alone for backward
compatibility, and try to add something
with the (library ...) syntax but with an
underlying semantics as much as possible
like the current module system.
Then I would write a paper or manifesto
on the exact reasons why libraries and
modules are too different to be inter-
changeable.
At least, that is how I would reconcile the
two approaches if I were even to begin
reconciliation. In the real world, I
will type my pipe dream to the mailling
list and then go to bed and not care about
it in the morning.
sounds reasonable. below is a work-in-progress sketch
that dreamers (-: or insomniacs who want to dream) might
find interesting. the manifesto is still bubbling, but
only time will tell...
thi
___________________________________________________________
[-- Attachment #2: where to put the parens?! --]
[-- Type: application/x-tar, Size: 4350 bytes --]
[-- Attachment #3: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-10-07 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 14:10 rfc (define-module ... #:use-modules ...) Thien-Thi Nguyen
2007-10-04 15:29 ` Ludovic Courtès
2007-10-04 18:40 ` Thien-Thi Nguyen
2007-10-04 15:30 ` Mike Gran
2007-10-04 16:29 ` Ludovic Courtès
2007-10-04 19:12 ` Thien-Thi Nguyen
2007-10-04 17:14 ` Clinton Ebadi
2007-10-04 19:09 ` Thien-Thi Nguyen
2007-10-04 19:21 ` Klaus Schilling
2007-10-04 19:18 ` Klaus Schilling
2007-10-05 23:47 ` Keith Wright
2007-10-06 9:59 ` Thien-Thi Nguyen
2007-10-07 4:05 ` Keith Wright
2007-10-07 9:37 ` Thien-Thi Nguyen [this message]
2007-10-07 14:23 ` Ludovic Courtès
2007-10-07 15:15 ` Thien-Thi Nguyen
2007-10-07 17:11 ` 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=87hcl36zb3.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=kwright@keithdiane.us \
/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).