29 Jul
2014
29 Jul
'14
3:15 a.m.
On 28/07/2014 17:41, Arran Cudbard-Bell wrote:
My inclination is to make '==' work as it used to in the users file and iterate over all instances of an attribute.
"and" or "or" semantics?
Then use attribute selectors [<inst>] :<tag> to limit the attribute used in the condition.
if (&foo == &bar) {
}
Would apply the operator to the cartesian product of &foo x &bar.
I can't say that particular syntax appeals to me. Postgres uses "any / all" for this, e.g. expr op [any|all] array-expr ...though I guess for consistency FR should be: expr op [first|any|all] multi-attr ...with "first" being the current behaviour?