In this particular case, it doesn't make a difference, but I've seen too many cases of people making a royal mess when they try and change code that uses C<or>.
This is one of those religious arguments which I just don't understand. As you say, in this particular case (and every case where it is a simple list of values to try), it doesn't make any difference. So indeed, where is the harm in using C<or> here. I think it is far more dangerous to rely on remembering the precedence order when constructing expressions (and hence I am prone to use a plethora of parentheses and a modicum of whitespace when it is even slightly ambivalent what I mean).
YMMV ;)
John
