[xacml] functions issues

[Simon Godik <simon@godik.com>]

I'm ok with the way 'or', 'and' are descirbed in the latest document:

 

'or': First to last, 'true' if one arg evaluates to 'true'. If any arg raises an error, return an ERROR.

'and': First to last, 'false' if one arg evaluates to 'false'. If any arg raises an error, return an ERROR.

In any case, if definitive result can be concluded, the rest of the args is not evaluated.

 

Here is a variation that forces all args computation, even in the presense of an error:

(Longer, but gives your a better chance to succeed):

 

Compute all 'and', 'or' args first to last. If 'error' is raised use it as placeholder until all computation is complete.

If 'error' could be substituted with either (true, false) without changing an outcome, return outcome.

Otherwise return error.

 

In any case, I do not see any errors being 'hidden', meaning changing an outcome of computation. 

Simply some errors are relevant and some are not.

 

I do not agree with defining error functions and default values.

 

Simon