it's also important to note that the s/// operator does not take a regular expression within it's second set of /'s. So escaping the (.) doesn't really do anything. Odd that it should make the warning go away.