Eternius wrote:
>
> Wiggins D Anconia wrote:
>
> >>Nilay Puri wrote:
> >>
> >
> >
> >>if u use an OS like linux (which will not write things imediately to
> >>disc) this forces it to do so.
> >>
> >
> >
> > That is misleading and not necessarily true. It tells Perl to unbuffer
> > the I/O but not t
then I guess, I didn't understand it myself
Wiggins D Anconia wrote:
Nilay Puri wrote:
if u use an OS like linux (which will not write things imediately to
disc) this forces it to do so.
That is misleading and not necessarily true. It tells Perl to unbuffer
the I/O but not the OS. The OS de
> Nilay Puri wrote:
>
>
> if u use an OS like linux (which will not write things imediately to
> disc) this forces it to do so.
>
That is misleading and not necessarily true. It tells Perl to unbuffer
the I/O but not the OS. The OS decides what will and won't get written
to disc, based on k
Nilay Puri wrote:
-Original Message-
From: Nilay Puri, Noida
Sent: Wednesday, February 04, 2004 11:37 AM
To: Perl (E-mail)
Subject: FW: special vars
-Original Message-
From: Nilay Puri, Noida
Sent: Wednesday, February 04, 2004 11:32 AM
To: Perl (E-mail)
Subject: speci
On Feb 4, Nilay Puri, Noida said:
>> Can any one help me understand the usage of special variable $| ?
>>
>> I know the description of this var. If set to nonzero, forces a flush
>> after every write or print.
Most filehandles buffer their output until a newline is reached. For
example, try th
