Re: Max 16384 bytes

in different code

Different from what? Whence comes this code, and what purpose does it fullfil?

From stat:

11 blksize preferred block size for file system I/O

The value 16384 comes from left-shift, it's 1<<14 Bytes or 2**14 Bytes or 16 kB. The expression you posted means:

If this filehandle's file system (if any) has no preference about I/O blocksize, I'll just use 16 kB.

Could be for socket I/O - hard to tell without context.

Note, your system is binary (hence 2) and 7 is a magic number (hence 14) :-)

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Comment on Re: Max 16384 bytes

Replies are listed 'Best First'.
Re^2: Max 16384 bytes by bloonix (Monk) on Jul 02, 2007 at 15:02 UTC
Okay, sorry, to less informations. If I try to sysread() or syswrite() more than 16k over a socket (IO::Socket::SSL) then only 16k are read or written and not more. So I try to find out why only 16k are written and saw this code but it did't gives me a answer.	[reply]
Re^2: Max 16384 bytes by Anomynous Monk (Scribe) on Jul 03, 2007 at 07:45 UTC
Maybe he meant "indifferent code"?	[reply]