If we know the pattern will never change, having it compile only once via the /o switch is great if the regex is in a loop. But if the target string is always going to be "Ovid" with an uppercase "O", that /i switch is killing performance (any monks feel free to correct my ad-hoc analysis).while (<>) { if (/Ovid/io) { # insert brilliant code here } }
In retrospect, perhaps coding practices like modularization and optimization should be totally separate issues and not dealt with in one post. Further, I realize that an entire book on these issues can be written (has been written?), so this may be beyond the scope of a simple post here on perlmonks. But these are burning issues for me and perhaps I seek instant gratification|nerdvana :)
Comments?
In reply to RE: RE: Good coding practices
by Ovid
in thread Good coding practices
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |