Bruno Desthuilliers <bdesth.quelquech...@free.quelquepart.fr> writes: > As I already stated, no technology can protect us from this kind of > error. Ask yourself why this module was reused as-is, instead of going > thru the whole specs / tests / QA process again, and *perhaps* you'll > start to understand why I say that language-enforced access > restrictions are the wrong solution to a real problem.
I have not seen anywhere that the specs stated that the sensor reading that overflowed that variable was supposed to be in range. It looks to me (but I don't know for sure) that the development process allowed an assumption to creep into the code that wasn't stated in the specs. -- http://mail.python.org/mailman/listinfo/python-list
