[WINED3D] Separate pshader/vshader tables

Ivan Gyurdiev ivg2 at cornell.edu
Wed Apr 26 18:34:50 CDT 2006


Clear all pshader codes from the vshader table and vice versa.

I remember suggestions to unify those two tables into one, but that does 
not make sense, and will create more problems than it solves. For 
example, two new version fields would have to be added to track min/max 
vs_version in parallel to ps_version. In fact, the opposite approach has 
been suggested on IRC where we break up each table per shader version. 
I'm not sure if that won't lead to lots of replicated information though 
- still thinking about that. 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: wine.remove_invalid_codes.diff
Type: text/x-patch
Size: 11579 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-patches/attachments/20060426/1b21befc/wine.remove_invalid_codes.diff


More information about the wine-patches mailing list