On Mon, Sep 26, 2011 at 3:57 PM, Ludwig Isaac Lim <[email protected]> wrote:
> Hi:
> Thanks for the quick response. Since according to definition of line
> buffering (see below), a buffer is flushed is after newlines, so writing
> statements such as :
> print "<p> This is a paragraph</p>\n"
>
> in a CGI program will automatically flush the buffer right? Or it
> doesn't? I wondering if perl will figure out that since STDOUT is not
> connected to a terminal, it will still buffer it even though the print
> contains a newline.
A look in the perlvar manual about "$|" should enlightened you,
especially in the part where *line buffered* and *block buffered* are
mentioned.
$ perldoc -v '$|'
HANDLE->autoflush(EXPR)
$OUTPUT_AUTOFLUSH
$| If set to nonzero, forces a flush right away and after every
write or print on the currently selected output channel.
Default is 0 (regardless of whether the channel is really
buffered by the system or not; $| tells you only whether you've
asked Perl explicitly to flush after each write). STDOUT will
typically be line buffered if output is to the terminal and
block buffered otherwise. Setting this variable is useful
primarily when you are outputting to a pipe or socket, such as
when you are running a Perl program under rsh and want to see
the output as it's happening. This has no effect on input
buffering. See "getc" in perlfunc for that. See "select" in
perldoc on how to select the output channel. See also
IO::Handle. (Mnemonic: when you want your pipes to be piping
hot.)
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
http://lists.linux.org.ph/mailman/listinfo/plug
Searchable Archives: http://archives.free.net.ph
