This clearly contradicts the doc that says: Nonexistence of either file results in "false". Which by extension means it should result in "false" if both files are nonexistent. --DD
unless "either" means "exclusive or". Looking at the code, this happens on purpose. No file equals No file has a certain kind of logic. Maybe we need to clarify the docs?
I personnally think it's a mistake, and often time comparing two non-existent files is simply a mistake, as it was for me. But I guess I'm not surprised I'm the only one who thinks different. So now I have experience with <filesmatch>, and I'll simply leave the next guy fall into the same trap I did, but at least s/he will have the benefit of some doc to explain the counter-intuitive behavior that goes against the principle of least surprise. Thanks Stefan, and nevermid. --DD
Who said it was just you? How about an additional attribute to control the behavior? I can see use cases for both results if both files do not exist.
Thinking about this, I think the default for nonexistent files is false too. It makes more sense using this as a test in a condition to decide whether to do something. If neither file is there, there isnt a match,.