-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jesse Barnes wrote:
> As to your example, I wasn't looking for theoretical issues, but real apps > that would depend on this behavior. I haven't played with many video apps, > so I'm not sure if what you outlined is common behavior, or if apps typically > care about much higher frequencies... That's a dangerous game to play. The spec is a contract between the API provider and the API user. If you deviate from it, some API user will eventually depend on that behavior, and you'll have to fix it after the fact. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmbUvYACgkQX1gOwKyEAw+hrwCgn6ydd32c0aIRKyPDpEpF84rJ tmMAoJZgVZGzSL1zOknyz2XD+CT+lW+9 =IN6p -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
