[vtk-developers] vtkGPUInfo and large amounts of memory

[Sean McBride]

On Mon, 7 Jul 2014 09:34:22 -0400, David Cole said:

>Right, but using size_t will still give you a potential overflow
>problem in a 32-bit pointer build... Shouldn't the type *always* be
>large enough to represent expected actual memory sizes encountered in
>the wild? And therefore, shouldn't it be something that's always at
>least 64-bits wide as "the other David" suggested...?

That's fine with me too.

So back to the original question: is such a change minor enough to not count as breaking API/ABI?  Or is it all just not worth it?  :)

Cheers,

-- 
____________________________________________________________
Sean McBride, B. Eng                 sean at rogue-research.com
Rogue Research                        www.rogue-research.com 
Mac Software Developer              Montréal, Québec, Canada