Re: Re: Re: STDIN to the Max?!?

See, I'm not even worried about the script, I'll make it work, that's not a prob. I was just wondering if anyone knew of any limitations on the amount of data that STDIN can handle, I probably should have made that more clear..

And tmiklas your right about it occupying more mem, but as you know, a @var handles multiple scalars which is what I want, in order to split the imputed data..

-- Yes, I am a criminal. My crime is that of defyance.

Comment on Re: Re: Re: STDIN to the Max?!? Download Code

Replies are listed 'Best First'.
Re: STDIN to the Max?!? by jeffenstein (Hermit) on Mar 22, 2002 at 15:47 UTC
STDIN shouldn't have a per-line limit. However, there may be a per-process limit to the amount of memory that you can use. Check out ulimit(1). The little snippet below will print a string of about 80MB, then read it back into a single scalar in perl. I just tried this out on my workstation, and it seems to work just fine. `perl -e 'print "a"x85000000' \| \ perl -e 'my $line = <STDIN>; print length($line), "\n";'` [download]	[reply] [d/l]

Replies are listed 'Best First'.

Re: STDIN to the Max?!?
by jeffenstein (Hermit) on Mar 22, 2002 at 15:47 UTC

STDIN shouldn't have a per-line limit.

However, there may be a per-process limit to the amount of memory that you can use. Check out ulimit(1).

The little snippet below will print a string of about 80MB, then read it back into a single scalar in perl. I just tried this out on my workstation, and it seems to work just fine.

perl -e 'print "a"x85000000' | \
perl -e 'my $line = <STDIN>; print length($line), "\n";'
[download]

[reply]
[d/l]