Re: Eval in context

The question isn't why we have a function that evaluates an expression in  
a context, but why we have two, where in other places we use one function  
with a variable number of parameters.

Steven


On Wed, 05 Feb 2020 13:20:28 +0100, Guntur Wiseno Putra  
<gsenopu@gmail.com> wrote:

> Dear Steven &
> public-xformsusers,
>
>
> S.P.: * ) Evaluates the string as an expression in the current context  
> *) Evaluates the string as an expression in the given >context.
>
> Is there a reason for this?
>
>
>
> G.W P:  Thinking of real lifes, daily lifes, of men:
> Expressions have contexts --they are contextual-- and they have meanings  
> to interpret and values to evaluate... ( That comes >from my a reading  
> of mine about meanings and values in relation with (human) existence.)
>
> Regard,
> Guntur Wiseno Putra
>
>
>
>
>
>
> Pada Rabu, 05 Februari 2020, Steven Pemberton <steven.pemberton@cwi.nl>  
> menulis:
>> Many functions have a variable number of parameters for special cases.
>>
>> For instance,
>>
>> valid()
>> valid(item*)
>> valid(item*, boolean)
>> valid(item*, boolean, boolean)
>>
>>
>> and
>>
>> string  serialize(item*)
>> string  serialize(item*, $params)
>>
>> (and others).
>>
>> And yet we have:
>>
>> item()*  eval(string)
>> Evaluates the string as an expression in the current context.
>>
>> item()*  eval-in-context(string, node()*)
>> Evaluates the string as an expression in the given context.
>>
>> Is there a reason for this?
>>
>> Steven