"Simonson, Lucanus J" <lucanus.j.simonson@intel.com> wrote in message news:33E1C72C74DBE747B7B59C1740F7443703593075@orsmsx417.amr.corp.intel.com... [...]
I forgot to mention that casting the pointer to signed integer will cause problems even if they happen to be the same bit width. This is because pointer values with a 1 in the msb will cast to negative integer values, which will cause the order of p and p+s to become inverted, leading to an error condition in numeric::interval, which will result in a null interval, according to interval's documentation. That would be difficult to debug.
Like previously mentionned that cast is simply a temporary solution but hopefully void * types will be easy to integrate into interval<>. I will also change int for unsigned until void * works. -Phil