Well, actually I completely ignore how new or old it may be, but I ignored its whole existence altogether, so... Whatever, it's study(). Is "to discover" the right verb for such a thing? Who knows... It was brought to my attention by a clpmisc post (news:1163429694.397139@proxy.dienste.wien.at) but it was a perldoc perlfunc away. I didn't know it simply because I can't remember having seen it mentioned anywhere in discussion or example before today. And discussions and examples are very important means for me to learn...
BTW, I selected "User Journal" as a "Journal Topic", because I can't see any that is just "Perl": would there have been a more appropriate one? Is the topic important anyway, or can one safely just stick with "User Journal"?
Re: (Score:1)
That’s because it’s only rarely useful and very nearly never a clear win. You may as well never think about it, and it won’t make a difference.
If you want to see another relic burried in perlfunc [perl.org] that’s even less useful, check out reset [perl.org].
I’m not sure selecting a topic even has any ef
Re: (Score:1)
Indeed I can't remember having used it, but I had seen it before. Actually I have a hard time judging whether it's more or less useful than
study(), although I'd rate it close to it. AIUI there's a difference though: the former has a semantic (side-)effect; the latter is only supposed to be (possibly) useful for speed optimization, but won't change what one's script will do in any way.I’m not sure s
-- # This prints: Just another Perl hacker, seek DATA,15,0 and print q... ; __END__
Re: (Score:1)
That’s sort of tautologic, of course; its entire point is the side effect.
I know. However, it takes time itself and rarely usefully speeds up a match, so in the general case, it will cause a speed hit (albeit usually a small one). The circumstances in which it can provide a measurable speed-up are so specific that in practice, the function is useless. And that’s why it doesn