W3C home > Mailing lists > Public > public-xformsusers@w3.org > February 2020

Re: Eval in context

From: Guntur Wiseno Putra <gsenopu@gmail.com>
Date: Wed, 5 Feb 2020 19:20:28 +0700
Message-ID: <CAKi_AEs=gnarOm7z2wfiVVXgHYXEemBwwN_PEeG0iKnB7o_n1Q@mail.gmail.com>
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: XForms <public-xformsusers@w3.org>
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
>
>
Received on Wednesday, 5 February 2020 12:20:32 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 5 February 2020 12:20:33 UTC