comment on

Ahhh... That's much more clear. I was (guessing) that unpack called in either context still split the entire row. The statement "In scalar context, it returns merely the first value produced." is a bit misleading. (To me anyway)

I read it to say that it still splits the entire row returning only the first value. Had this been the case, then the memory would've been allocated already. To store each value. If each value is stored very quickly internal to unpack, why would it take longer to copy it to a new structure. That isn't true and now I understand what is really happening. 8)

As always this is a great resource for those of us that haven't read the source to perl. (Do you blame me. It's huge! ;) Even if I did, I'm not certain I'd understand it anywhere near as well as you all do.)

Thanks for the clarification. I really appreciate it!

Shawn M Ferris
Oracle DBA

In reply to Re: Re: Re: Re: Assining data to an array is slow.. by smferris
in thread Assining data to an array is slow.. by smferris

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.


P is for Practical
	PerlMonks