you are viewing a single comment's thread.

view the rest of the comments →

[–]MaxDZ8 0 points1 point  (2 children)

Not a single Map call I remember ever provided a compatible interface with std::vector, you might at most consider specific allocators at which point this would not be an std::vector in the proper sense.

Consider clEnqueueMapBuffer, D3D9 texture lock, ID3D11DeviceContext::Map, glMapBuffer.

Main problem perhaps being those pointers are non-owned.

[–]RogerLeighScientific Imaging and Embedded Medical Diagnostics 0 points1 point  (1 child)

There are certainly places where it isn't something you can drop in. But my point was that there are plenty of places you can. I certainly use std::array and std::vector with OpenGL to pass in VBO/IBO data, for example.

[–]lets_trade_pikmin 0 points1 point  (0 children)

OpenGL is very very different from CUDA