Note that your fastest case is also the only one that doesn't handle long lines. I find it a pretty poor benchmark to reimplement a module's logic badly and then wonder if it runs faster. Fix the 'rawio' case to handle things as well as File::ReadBackwards (and the other cases) do(es) and it'll be closer in speed. I'm sure it will still be faster, since it doesn't use tied handles or actually deal with a general purpose problem.

But I'd still use File::ReadBackwards or "tail" since I don't find "get last line of a file" to be something I care to heavily optimize on the few occasions when I do it and the code to properly handle all of the boundary cases is not something I care to maintain on its own.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.