On Thu, Aug 02, 2001 at 11:55:35AM -0700, Paul wrote:
>
> --- Michael Fowler <[EMAIL PROTECTED]> wrote:
> > AFAIK, print is not special-cased to read chunk by chunk. In
> > fact, it's more ineffecient than simply slurping the entire file in
> > and then printing it. The syntax is equivalent to
--- Michael Fowler <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 02, 2001 at 09:20:43AM -0700, Paul wrote:
> > print ;
> >
> > If IN is accessing a large file, does the second syntax try to
> > slurp the whole thing into memory before printing it? Or is there
> > some internal optimization that dol
On Aug 2, Michael Fowler said:
>You can only print a string. When print is given multiple arguments it
>joins them with $" before printing. This is documented in perldoc -f print.
*Cough* $, not $".
$" is used when you put an array (or array slice) in double quotes.
And, upon checking the
On Thu, Aug 02, 2001 at 09:20:43AM -0700, Paul wrote:
> print ;
>
> If IN is accessing a large file, does the second syntax try to slurp
> the whole thing into memory before printing it? Or is there some
> internal optimization that doles it through in bufferloads?
AFAIK, print is not special
On Thu, Aug 02, 2001 at 03:46:22PM -0400, Jeff 'japhy/Marillion' Pinyan wrote:
> On Aug 2, Michael Fowler said:
>
> >You can only print a string. When print is given multiple arguments it
> >joins them with $" before printing. This is documented in perldoc -f print.
>
> *Cough* $, not $".
>
>
