Beepster
So if the function is one that isn't intended usage can it really be considered a bug?
Good point, Beepster. I've done a fair bit of coding and worked in several companies where coding was going on (even when I was not coding).
Normally, if an operation isn't supported and the code is nice and clean, anything like what I described above should have a default behavior of.. well, no behaviour. Nothing should happen. Execution should simply 'fall out the bottom' and go back into the main wait loop looking for further input from the user.
So, if the software locks up, the implication is that the code is somehow going down an execution path that's not intended. If that happens, there has to be some bad or mangled code somewhere and that constitutes a bug. At least, that's my reasoning.