I was just going to post that as well. This is also exactly the kind of thing that checked arithmetic performance would not be an issue for.
jack. On Wed, May 8, 2013 at 4:33 PM, Ben Lerner <[email protected]> wrote: > Timely bug: today's explanation of the Diablo3 gold-duping market crash. > http://pastebin.com/YYPM4uQK > > > On 4/29/2013 10:43 PM, Jack Moffitt wrote: >>>> >>>> For the most part, nobody checks. They weighed the cost of those errors >>>> against the potential performance loss and decided they would prefer to >>>> go fast. >>> >>> In C the checking is just too ugly without operator overloading. In C++ >>> you >>> can make it look nice, but it's a lot more expensive than it could be if >>> you >>> had compiler support, I expect. Even so, in the browser we write a lot of >>> checking code. Other browsers do too. >> >> I came across Tim Sweeny's POPL presentation[1] again today and >> spotted page 30 where he claims 50% of the bugs in AAA games come >> from: >> >> - array bounds >> - deref of null pointers >> - integer overflow >> - accessing unintialized vars >> >> >> http://www.st.cs.uni-saarland.de/edu/seminare/2005/advanced-fp/docs/sweeny.pdf >> >> jack. >> _______________________________________________ >> Rust-dev mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/rust-dev >> > _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
