case-sensitivity: bug or feature in query-replace?

following the recent patch on isearch about case-sensitive searches, i've been using query-replace to fix a file where i typed 'objectname' instead of 'objectName' (the 'N' is important), but i already had about a thousand instances of 'objectName' around and several 'ObjectName' as well. so i wanted to replace all instances of 'objectname' with 'objectName', and the replace matched all three forms. now i know the replace is case-sensitive if the FROM argument has case, but should it not be case sensitive as well if the TO argument has case when the FROM does not have ? or would it make sense not to? anyways, the replace worked for all instances, because objectname => objectName ObjectName => ObjectName objectName => objectName so it did after all what i wanted, but still it did match 'ObjectName' which i didn't want it to match. actually i think it would make sense to make it case-sensitive if there are case in any of the 2 arguments . tell me i am wrong, or better make this an option, or am i so wrong i don't deserve an option ? :-/ -- # Stef Epardaud, # There is no limit to the power of computing ... # Java Defeater # ... except men maybe ? # Earth # Lunatech Research, # Solar System # soon we will quit researching and start finding...