-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 2013-09-17 17:12, schrieb Henri Verbeet:
The point is that the distinction you're making here between
volumes and everything else is a bit arbitrary, and I think this
patch as it is will make it more work rather than less to move
towards having a set of capability flags per resource type. The
advantage of the alternative is mostly that it's less invasive, so
easier to change later.
I might have misunderstood what you meant with "separate flags for
each GL resource type". Did you mean something like this
B8G8R8A8_UNORM.flags[texture2d] = RENDERTARGET | TEXTURE | ...;
B8G8R8A8_UNORM.flags[renderbuffer] = RENDERTARGET | ...;
B8G8R8A8_UNORM.flags[texture3d] = TEXTURE | ...;
Instead of
B8G8R8A8_UNORM.flags = RENDERTARGET | TEXTURE2D | TEXTURE3D |
RENDERBUFFER | TEXTURECUBE | ...; ?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iQIcBAEBAgAGBQJSOKiCAAoJEN0/YqbEcdMwdzwP/2+jmNXdtZNJY6KOFXgAXAS9
qvER27doBcBdgBYfOn+1EuntCqFgF/mWFdt4Qt9bsNsjoffli90vjymmW58CgXjl
6403DPS17Zw01dWQYtNIeIDdzP74pcIuIbaZ9l63XDDk/k42ne4VleJW2UehQT8/
91Ft/K1puR/ENQ8ka9WxAirJAqV7CV7hgpUrraAE0xWNXD3tXhDnVvEL9bnuk226
gGm8jeDsl8GX9/LL+Lcud5KK1R66xD5SJCbL8rXmZijiq5molBLMMDO6HMV2z9Zf
XDFekLqTs51pQjNc163yoKa3vfA0sUa2tOwA+KzPTuiimowAZy8qS6CkAyhJGOJn
aTiCOLW6p3Ywsct6NkRwKXjbbi6RJcXRbKsLsBklHPFrhmNthbgdQoKkdDX+G3qZ
+kG7N8w402bvNqUv4eZ3d6vwwrKd2ma35kjw/CrTObliQfWgPmSQM1gXA+zGtkPc
q/1e1VufQ34+QI7osIIdpl5uIaeg/gGrYB1qCjSmpQQWUiJB2WfLRLj2Czw0+uUJ
gTK41YrU3axBQOl7NuZu8d6P1RkSfyZkFUX6abfF8NGFCn4CSOXuCOr5GlEblI9O
o2s0cKH43Zu+s/mk4xsnb2pR+WiKSU1vFrrvLFIecP07y53w4eqxhaL7CcEBphOu
3kYjieSGTr6zGho/PaNF
=vnJi
-----END PGP SIGNATURE-----