From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: Smart variables, dumb variables
Date: 14 Aug 2002 23:45:21 +0200 [thread overview]
Message-ID: <87r8h1ru6m.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87znvpf7pr.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Hmm, my initial reaction is that this kind of "transparency" always
> makes me nervous.
Yep, me too. However, I don't think that we should categorically deny
people this opportunity because we think it might be abused.
> [...]
> However, I understand the reasoning, so I wonder whether or not we
> might be able to come up with a broader solution (as you alluded to)
> to start with.
What I'm interested in right now is to have a way to force all
variable access thru a common point. Whatever we do at that point is
still open.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-14 21:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 20:06 Smart variables, dumb variables Marius Vollmer
2002-08-14 8:07 ` tomas
2002-08-14 19:35 ` Marius Vollmer
2002-08-14 20:28 ` tomas
2002-08-14 20:48 ` Marius Vollmer
2002-08-14 21:06 ` rm
2002-08-14 21:09 ` Marius Vollmer
2002-08-15 8:06 ` rm
2002-08-15 8:01 ` Lynn Winebarger
2002-08-15 9:51 ` rm
2002-08-15 14:44 ` Rob Browning
2002-08-15 16:34 ` Marius Vollmer
2002-08-15 17:27 ` rm
2002-08-15 19:43 ` Marius Vollmer
2002-08-15 20:02 ` rm
2002-08-15 20:02 ` Marius Vollmer
2002-08-15 20:25 ` rm
2002-08-17 11:59 ` Neil Jerram
2002-08-19 23:29 ` Marius Vollmer
2002-08-20 12:01 ` rm
2002-08-26 22:06 ` Marius Vollmer
2002-08-15 10:52 ` tomas
2002-08-15 16:36 ` Marius Vollmer
2002-08-14 21:31 ` Rob Browning
2002-08-14 21:45 ` Marius Vollmer [this message]
2002-08-15 2:43 ` Rob Browning
2002-08-15 6:29 ` Marius Vollmer
2002-08-15 14:38 ` Rob Browning
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=87r8h1ru6m.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).