Re: Bug in eval-string?

[Marius Vollmer]

address@hidden 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.)

> 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.  Most of this is
implicit and applies to all of the documentation.  Do we need to make
this more explicit?

> 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.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405