Nope. And heres why.

The /o modifier relates specifically to interpolated variables inside of the regex. For instance, the regex:

m/$matchvar/

Is a candidate for the /o modifier, since it will be built from the value of $matchvar. With the /o modifier, the resulting "regex engine" will be cached for future use. The next time we run across this regex, we'll use the same engine, even if $matchvar has changed.

The common analogy is that the /o modifier is like a promise. You promise not to change any of the variables in the regex, in return for better performance. If you break your promise, your program will break as well.

Your original regex has no interpolated variables, so the regex is only compiled once and we use that copy everytime regardless of the /o modifier.

In other words, the /o modifier would be redundant on your regex.

-Blake