On 8/1/2012 3:44 PM, Bernard Helyer wrote:
I would be concerned with potential performance ramifications,
though.
As well you should be. A poorly constructed range can have terrible performance.
But one thing to take careful note of: you *can* define a range that is nothing
more than a pointer. Of course, you must be careful using such, because it won't
be safe, but if performance overrides everything else, that option is available.
And best of all, one could still supply a safe range to the same algorithm code,
without changing any of it.
