I think this "feature" is for sed compatibility. (By compatibility, I mean that the people using sed can get used to perl easier.)

Maybe it would be better if this magic applied only if the regexp is empty before interpolation (and before overload qr transformation).

This kind of thing keeps me humble, because I know that somewhere there is someone who understands exactly why this was a good idea

Its still a good idea:

if (/foo/ or /bop/ or /fnorble/) {
  s//baz/;
}
[download]

IOW, it means you can have several regexes try to match, and then without having to worry about which one did you can then replace the thing that was matched. I only recently came accross this feature, but sice I have its found its way into more code than I thought it would.

Huh?

s/foo|bop|fnorble/baz/;
[download]

Makeshifts last the longest.

Fair point. The example is not the best I've ever written.

The point is that the empty regex behaviour is useful for allowing you to use m/.../ and then later s//.../ without having to match a second time. Maybe this is better

if ($foo and /bar/) {
   print "Condition suceeds.\n";
   if ($bloop and /bop/) {
      #...
   }
   # do other stuff, maybe even exit...
   s//baz/; # switch bar or bop with baz depending 
            # on a bunch of things that have already happened.
 }
[download]

Hopefully now you see the point? Sure we could probably rework the logic so this isnt needed, but I like the possibilities this opens up. :-)



---
demerphq



First they ignore you, then they laugh at you, then they fight you, then you win.
-- Gandhi