invented wrote:dmcconachie wrote:Not when they're pretty much irrelevant, have no real impact on the function of the app and would require a rewrite of the code.
"Irrelevant" is subjective. It's a bug, probably not a big one, and should be fixed. Opting to do things half-assed is not the way to code.
Its not even a 'bug'. All measurement instruments have limitations - especially digital ones. Analog instruments, which in theory at least have an infinite range of values are often connected to computers by an analog-to-digital converter which slots ranges of values into discrete digital quanta. This immediately introduces an imprecision or 'bug' if you like. For example, I have a measuring device (it actually measures resistance but that is irrelevant) that outputs a current between 4 and 20 mA - a very typical scenario. This is connected to another device which contains an a/d converter that outputs a number between 0 and 127. I configured this device to output a number from 0 to 100 and thought no more about it. I was interested in the shape of the distribution and was mildly irritated some months later to get a typical bell shaped curve but with spikes at approximately every fourth value. The reason was simple 128 values were being squeezed into 101 values so 27 of them were getting doubled up. There was no way I could give the end user a properly shaped curve and the intuitive 0-100 scale they expected. I changed the output to 0-127 and simply told the users that 0-100 was impossible! The point is that ALL instrumentation has limitations and my example above is exactly inversely analagous to what is happening with the 60MPH problem. Here a smaller number of values (in knots) is being distributed into a larger number of buckets (mph) so some of the buckets have no value to throw into them. Its not half-assed - just a different number of asses on each side of the problem! Its not a bug. You are simply asking for the impossible! There is no definitively right scale in which to measure speed. Why not get modern and forget your archaic miles anyway. Switch to kms where the number of empty buckets will be even greater!