Dunno about that, I learnt/found out about it via a presentation at YAPC::Europe::Paris. Perhaps i missunderstood the meaning of that part of the presentation...
None the less, i'm off to look at your node.. | [reply] |
I noticed that MJD has recently updated the slides for his Regular Expression Mastery talk (could this be what you saw at YAPC?), and despite having changed several slides, this one is still a part of persentation set, so presumably, he thinks /o still has some value.
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
If I understand your problem, I can solve it! Of course, the same can be said for you.
| [reply] |
I personally use /o, but only when it actually means something. In my case the package has a "constant" in a global variable (I'm just not using a `use constant ...`) and the constant is used in a regex. In that case I know that perl is going to keep re-interpolating the variable on every execution and the /o just prevents that. The actual regex wouldn't be compiled more than once because the constant wouldn't change, I just get perl to save some work later. The idea here is that /o is *all* about interpolation. If you aren't interpolating anything then it has absolutely no point.
| [reply] |
