Inside VectorStorm, there’s a function vsClamp; it looks like this:
#define vsClamp(a,min,max) ( vsMin( max, vsMax( min, a ) ) )
(modified for legibility; C/C++ coders, no need to warn me about how painfully dangerous that code snippit is. :) )
You’d use it like this:
vsClamp(1, 0, 10) -> 1 vsClamp(0, 10, 20) -> 10 vsClamp(6, 2, 3) -> 3
Effectively, you give it a number, and then a minimum and maximum legal value; the value that pops out of the other end is the original number, clamped to within the requested range.
But what I’ve just discovered is that about half of my code is actually calling this function like this:
vsClamp( min, a, max );
That is, it sandwiches the value to be clamped between the minimum and maximum values. Which actually makes a weird kind of sense, but isn’t how I actually implemented that function. “Oh no,” I thought, “all that code is going to be doing totally the wrong thing”
But as it turns out, calling vsClamp( a, min, max ) is identical to calling vsClamp( min, a, max ), which is itself identical to calling vsClamp( min, max, a ). As long as whichever value you intend to act as the ‘min’ is less than whichever value you intend to act as the ‘max’, all three are guaranteed to return the same result.
How bizarre is that? :)