Yeah... I hadn't considered that specifically, but I have been thinking about another issue to do with the idea of robots and androids and the like...
Slavery.
I kept throwing around an idea for a thread, but couldn't quite bring myself to do it.
But in short, we seem to love having slaves.
We have a long history of keeping other humans as slaves (and enslaving animals for various reasons as well)
While in recent history the first thing that comes to mind is declaring people of a certain race to be slaves, slavery has a much longer and more diverse history than that...
Of course, we've gone beyond that, right?
... Or have we?
See...
This idea of destroying an intelligent android, (that can clearly feel pain, and think to some extent) is merely one facet of a wider concept.
The reason why this could come about is not merely a natural extension of what some of us currently do with our posessions and gadgets, but in fact, an extension of the idea of ownership.
I
own my computer. But... If my computer was an intelligent being in it's own right, would I have any more right to claim ownership of it than I would to claim I owned another human being? (As in, as slave?)
For that matter though, since an android is created and programmed with a specific purpose in mind (hypothetically), if you ask it, it may well say it enjoys it's function, and lives only to please...
But even so, does the fact that it is happy for me to 'own' it, and do whatever I ask it to, make it any less of a slave?
And does the fact that I own it, and it is a machine, technically actually give me the right to do whatever I please to it? (such as the example given in the OP)?
Dirty Hipsters said:
The combination of these things and many others makes physical pain kind of a lousy way to diagnose problems within the body. It's imprecise and can trigger completely unnecessarily. It's useful to humans because we have no other way to diagnose problems within ourselves, but considering the problems with pain, if we were to design a robot that was self aware we'd most likely find a much more practical solution to the problem of how to let it know that something is wrong with it.
I think your description of the situation kind of answers itself in some ways. Not that it's a useful mechanism compared to the possible alternatives, but what all your examples actually demonstrate is that pain is not a sensation of "this is bad, stop doing this", as it is "Something in this area is damaged! Watch out!"
Even the example you gave of tearing the muscles. - That may be good for you long-term, but in the immediate here-and-now, you have, in fact damaged your muscles.
Were it not for our innate regenerative abilities, that would definitely not be a good thing.
As it is, because our body does regenerate and regrow things in a way that improves them, this can be a good thing long-term, but it is still an example of you damaging yourself in the immediate sense.
Pain you can't do anything about is... Well, a consequence of a system that only cares about damage, and not specifically what to do about it.
I mean, in theory, you could implement a whole heap of other kinds of systems to take over this task, but it's very hard to say with a subject like this what that would look like in the end.
(or what it 'feels' like to the android itself. Which is an innately unknown factor)
Of course, when you consider this more closely, making an android feel pain has the hypothetical benefit of making a human being more sympathetic to what they are doing to the android.
In this case the function of pain in an android has nothing to do with what the android actually feels (if it feels anything at all), but rather, it's behaviour would be tuned to attempt to elicit a certain kind of emotional response from the humans around it.
Which, admittedly may not work in the slightest, but...
It's something that's worth keeping in mind.