comment on

A parser which consumes the string would be an example application.

I agree that in many cases the caching is going to hide or eliminate the problem, and in fact, it was a little tricky to compose the original example.

However, in code that doesn't need to know the actual length of the string in characters, it's poor practice to use length(), whose cost scales with the size of the string on SVf_UTF8 scalars. The advantage of bytes::length() is that it's basically a lookup on a member of the SV struct. There's a little bit of extra math to deal with offsets, but it's still O(1) rather than O(n).

The ne "" idiom is also O(1) because it's just checking to see whether the total byte size of the string is 0, not counting characters and seeing if the count is 0. Which makes it an effective replacement.

In reply to Re^6: Alternative to bytes::length() (7% solution) by creamygoodness
in thread Alternative to bytes::length() by creamygoodness

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks