You've solved a non-trivial problem in a trivial fashion. That's bound to cause problems. Running a blind sed on your perl code is inadvisable, to say the least. There's no way for either of your examples to *not* make an inappropriate change in comments, pod, or any string that happens to contain 'and':

   sub sandbox {
     my ($this, $that) = @_;
     blarf($this) and mungle($that);
     # etc.
   }
[download]

Both of your examples will re-write that as:

   sub s&&box {
     my ($this, $that) = @_;
     blarf($this) && mungle($that);
     # etc.
   }
[download]

Plus, there might be other programmers working on the project that don't have this and and && confusion. As you've already realized, there's no quick fix for the OP. Either examine each file, or put a bit more time into writing a smarter parser.

I did ++ you for having one saving grace: re-writing the code to temp files rather than over the original code, and keeping the original stuff around.

I know that this is stuff you already realized - but there's a few other replies similar to yours, and I happened to choose yours to reply to :)

blyman
setenv EXINIT 'set noai ts=2'