It is common to use SWAP to put two items in ascending order, like this:

DIM ONE, TWO AS LONG
' ...

IF ONE > TWO THEN SWAP ONE, TWO
This type of code is so common, it would be convenient to combine the two actions into one. Suppose we called this capability ORDER. Then, the code above could be shortened to,

ORDER ONE, TWO
It would not make sense for SWAP to take anything other than two operands, but for ORDER, it would. So, there is no reason why ORDER couldn't arrange the values of multiple variables in ascending order:

ORDER ONE, TWO, THREE
In the ORDER statement (or function) each variable would have to be of the same type.

If ORDER were designed as a function rather than a statement, the returned value could be boolean, with TRUE being returned if any rearrangement of values occurred, otherwise FALSE.