What the docs actually say is:
SCALAR will be grown or shrunk to the length actually read.
I take this to mean that SCALAR will have the number of bytes read, but not regardless of LENGTH. If the number of bytes read is less than LENGTH (e.g. the socket has closed), then the length of SCALAR will be less then LENGTH as well. If however, there are more bytes in the socket's buffer than LENGTH, SCALAR will contain LENGTH bytes, and the remaining bytes stay in the socket buffer.

So, the actually read part is specified for the case where you read less bytes than LENGTH.

As to dynamically increasing LENGTH, I do not know what you mean exactly, but you can specify a different length in different recv()'s:

recv($socket, $string1, 512, 0); recv($socket, $string2, 256, 0):

CU
Robartes- hoping this makes some sense


In reply to Re: recv byte length problem? by robartes
in thread recv byte length problem? by peschkaj

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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! —
  • 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:
    & &amp;
    < &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.