From: Tom Lord <lord@regexps.com>
Subject: Re: new-model.text, please comment
Date: Sat, 14 Sep 2002 17:50:56 -0700 (PDT) [thread overview]
Message-ID: <200209150050.RAA10986@morrowfield.regexps.com> (raw)
In-Reply-To: <87sn0cp4qg.fsf@zagadka.ping.de> (message from Marius Vollmer on 15 Sep 2002 00:48:39 +0200)
> Anyway, I actually try to avoid a discussion about what kind of module
> system we want, whether it should allow incremental, interactive
> modifications, or whether it must allow closed-world compilation ala
> Stalin.
> I hope that the model allows both.
Yay. I think your hope expresses a long-standing Guile design
principle/design pattern, so I'll reinforce it by paraphrase.
One principle/pattern:
Maximize sensible interactive/dynamic/reflective capability
(up to but not including features that can crash an
interpreter).
complemented by a design principle/design pattern that was always in
the back of my head but never came up in the work I did:
Provide and document sensible subsets to which code can
be restricted to support excellent compilation.
In other words: find the really nice interactive, incremental system
of which a stalinesque system is a clearly and usefully defined
subset.
"Blow off native threads and make () == #f" -- from the big list of
pointless advice :-)
-t
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-09-15 0:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 18:05 new-model.text, please comment Marius Vollmer
2002-09-12 22:48 ` Tom Lord
2002-09-14 22:48 ` Marius Vollmer
2002-09-15 0:50 ` Tom Lord [this message]
2002-09-15 0:55 ` Tom Lord
2002-09-21 20:27 ` Marius Vollmer
2002-09-12 23:28 ` Rob Browning
2002-09-13 20:22 ` Marius Vollmer
2002-09-13 20:34 ` Rob Browning
2002-09-13 18:53 ` Neil Jerram
2002-09-13 22:06 ` Rob Browning
2002-09-14 1:15 ` Lynn Winebarger
2002-09-14 22:05 ` Marius Vollmer
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=200209150050.RAA10986@morrowfield.regexps.com \
--to=lord@regexps.com \
/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).