Matt Turner <matts...@gmail.com> writes: >[...] > Indeed. And another thing to consider is that we've discussed > compiling with -fno-exceptions. >
Heh, the benefit you get from doing that is virtually zero. And in cases like this where failure would have to be handled many levels up in the stack and require redesigning an interface used in hundreds of places making it more awkward to use, not using exceptions is a really strong incentive not to handle failure at all. I cannot see any better solution here other than throwing an exception or letting the program segfault. > I think it's okay to add out-of-memory checks where we can reasonably > do something about them, but code churn *just* to silence a tool (one > that I'm not aware of catching any meaningful bugs) doesn't seem good.
pgpjB4K6F7rAt.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
