hi, quite a while ago the max() and min() functions were extended (IIRC) to also allow matrix arguments, to avoid having to write something like maxc(maxr(...)). So "max(ones(3,1))" has worked for some time. First of all, I've just noticed that this is not reflected in the function reference / docs, where only series and list arguments are mentioned. Secondly, this extension of max() and min() means that "xmax(a,b)" can easily be written as "max({a,b})". I therefore wonder whether we should keep xmax() and xmin(). Furthermore, perhaps max() and min() could be extended even further to allow two scalar arguments, such that "max(a,b)" would become an alias of "max({a,b})", to ease the transition from xmax() and xmin(). There are of course obvious backwards-compatibility issues, so this should perhaps also be discussed on the users' list. But still; I've always found xmax() and xmin() a bit weird... thanks, sven