Currently only scalar input arguments are allowed, thus a scalar function of, normally, two scalar inputs is implemented.
A significant advantage is provided to adopt the m-code to vector input arguments, i.e. XSteam as vector function.
This should be achived by not using for-iterations due to high computational effort and due to non-usage of Matlab specific advantages in vector arithmetic.
The function z=f(x,y) (where f is any property function, z the dependent variable and x,y the independent properties) should allow following calls:
x and y in R(1) => z in R(1) (as actual implementation does)
x in R(n), y in R(1) => z in R(n) (y is then constant for all x)
x in R(1), y in R(n) => z in R(n) (x is then constant for all y)
x in R(n), y in R(n) => z in R(n) (i-th element in x corresponds to i-th element in y)
This additional feature would be downward compatible and achieve a huge advantage in productivity.