The warning is intended to warn you that perl and you might have thought differently on how that statment was phrased, it is not intended to babysit you.

But you see, perl and I thought exactly the same on how the statement was "phrased", we both thought that "print (...)" was a function call. It's that perl thought I thought that perl thought differently. And that's where I think it goes too far. Such warnings are wrong too often, and warnings that are wrong too often are worse than not having warnings at all.