I do something like:

(const GLvoid*)(uintptr_t)attributes["vertexPosition"].byteSize

So I'm casting to a uint with a size that matches a pointer before casting to a pointer.

Someone who doesn't like c style casts will probably chime in and tell us that code is horrible (they may well have a point) :)

Someone who doesn't like c style casts will probably chime in and tell us that code is horrible (they may well have a point)

First things first. Since you are using C++, why are you using horrible C casts? There is static_cast and reinterpret_cast.

First things first. Since you are using C++, why are you using horrible C casts? There is static_cast and reinterpret_cast. They show intent much clearer, are easier to locate when searching a document and actually avoid some of the potential pitfalls of C casts.

Then, a way to solve the warning is to use

static_cast<const char*>(0) + size

Or, if the editor decides to mangle my template again turn a null pointer into a const char* pointer and add your offset. Good old pointer arithmetic will then deal with the rest.

In this particular case, I don't see the point of making a stink about it. OpenGL's the one doing an abusive integer-pointer cast and there's no particular ambiguity about what's happening, or particular potential for unexpected behavior. So C or C++ style cast, do whatever. Hilariously enough, your idea of adding to a zero pointer? Undefined behavior. Whoops. It's just a messy thing to do in the first place.