On 29 Jul 2014, at 03:15, Phil Mayers <p.mayers@IMPERIAL.AC.UK> wrote:
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?
or
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?
Sure... Though We already use [*] for string expansions, Alan suggested using the same here to refer to multiple instances. Do you think that'd work ok? Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2