The intent of the second paragraph of 2.14.9 is to call out a special case that overrides the general behavior described in the other places you mentioned. Not a self-contradiction; just a special case that applies only when all the conditions mentioned in the paragraph are met.
As the comments in runOne() indicate, other tests in glean may depend on being able to write exact values into the framebuffer. If you mask the actual behavior by allowing more slop in ExactRGBA, you might see failures in other tests that are more difficult to track down because ExactRGBA appears to pass. I don't have time to look at the moment, but if any test explicitly examines the results from ExactRGBA, this problem is likely to arise. Allen ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
