On 01/12/16 08:55, Xiang, Haihao wrote:
> Instead the user must call vaDestroyBuffer() to destroy a buffer explicitly.
>
> If following the previous API specification,
> 1. Violate "who allocate who release" principle
> 2. The user cannot re-use VA buffer flexibly
> 3. The user still has to call v
Instead the user must call vaDestroyBuffer() to destroy a buffer explicitly.
If following the previous API specification,
1. Violate "who allocate who release" principle
2. The user cannot re-use VA buffer flexibly
3. The user still has to call vaDestroyBuffer() to destroy the buffers which
are