On Thu, Aug 15, 2013 at 5:59 AM, Simon Urbanek
wrote:
> Note that this is documented very explicitly:
>
> "evalÂ’ evaluates its first argument in the current scope before passing it
> to the evaluator"
>
But the same man page also describes "eval" like this:
'eval' evaluates the 'expr' argument
Part of the confusion actually comes from the overspecificity of the
documentation. When the actual majority of the verbiage in a manual page is
given to how a function "evaluates" its argument, one tends to infer (by
the flouting of Grice's maxim of quantity) that this term "evaluation"
refers to
On Aug 15, 2013, at 3:06 AM, Gabriel Becker wrote:
> On Wed, Aug 14, 2013 at 11:14 PM, Peter Meilstrup > wrote:
>
>> I agree that the present behavior of withVisible is the Right Thing, but
>> the documentation is confusing. The documentation claims that withVisible
>> "evaluates an expression."
On Wed, Aug 14, 2013 at 11:14 PM, Peter Meilstrup wrote:
> I agree that the present behavior of withVisible is the Right Thing, but
> the documentation is confusing. The documentation claims that withVisible
> "evaluates an expression."
>
> This may capture an inside view of how the .Internal fun
