From: rm@fabula.de
Cc: rm@fabula.de, Neil Jerram <neil@ossau.uklinux.net>, guile-devel@gnu.org
Subject: Re: Bug in eval-string?
Date: Mon, 12 Aug 2002 12:49:42 +0200 [thread overview]
Message-ID: <20020812104942.GA2209@www> (raw)
In-Reply-To: <87y9be6ag7.fsf@zagadka.ping.de>
On Sat, Aug 10, 2002 at 04:43:36PM +0200, Marius Vollmer wrote:
> rm@fabula.de writes:
>
> > I think i (wrongly) assumend that eval-string is "syntactic sugar"
> > for eval.
>
> There is a big difference between a macro and a function. Why did you
> think that eval-string is a macro? (The documentation of eval-string
> says that it is a procedure.)
Because sometimes, late at night, i tend to overlook the obvoius --
this is a sign of age, you'll experience it too ;-)
> > maybe the documentation should be modified:
> >
> > "Evaluation takes place in the environment returned by the\n"
> > "procedure @code{interaction-environment}.")
> >
> > to
> > "Evaluation takes place in the same environment as \n"
> > "returned by the procedure @code{interaction-environment}.")
>
> I don't see the difference between the two. The question is, for
> both, what is "the procedure interaction-environment". The name
> refers to the procedure bound to the global variable that is named
> "interaction-environment" in the guile-core module.
Hmm, my english is probably not as clear as i want it to be: from the
first version i get the impression that by modifying the procedure
'interaction-environment' i have control over the environment in which
'Eval-string' takes place. The second version tries to be a bit clearer
over the fact that 'interaction-environment' just returns the environment
(of course, since eval-string isn't a macro this is pretty much of no
importance).
> Most of this is
> implicit and applies to all of the documentation. Do we need to make
> this more explicit?
I think 'eval-string' takening an optional parameter is cleaner.
> > Wouldn't the 'eval*' interface be clearer and more orthogonal if
> > eval-string would have a second, optional parameter specifying the
> > environment/module in which evaluation should take place.
>
> Yes, this sounds good to me. I will make that change.
>
Thanks
Ralf
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-12 10:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 12:56 Bug in eval-string? rm
2002-08-08 21:03 ` Marius Vollmer
2002-08-09 9:06 ` Matthias Koeppe
2002-08-09 9:19 ` Marius Vollmer
2002-08-09 10:24 ` Matthias Koeppe
2002-08-10 14:18 ` Marius Vollmer
2002-08-12 18:20 ` Matthias Koeppe
2002-08-13 0:39 ` Marius Vollmer
2002-08-14 19:07 ` Marius Vollmer
2002-08-17 11:09 ` Neil Jerram
2002-08-20 11:39 ` Matthias Koeppe
2002-08-21 19:26 ` Marius Vollmer
2002-08-27 14:18 ` Emacs variables (was: Bug in eval-string?) Matthias Koeppe
2002-08-31 13:51 ` Marius Vollmer
2002-08-08 21:27 ` Bug in eval-string? Neil Jerram
2002-08-09 9:35 ` rm
2002-08-10 14:43 ` Marius Vollmer
2002-08-12 10:49 ` rm [this message]
2002-08-13 20:55 ` 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=20020812104942.GA2209@www \
--to=rm@fabula.de \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).