Craig A. Berry wrote:
At 4:19 PM -0400 10/22/05, John E. Malmberg wrote:
My guess, though I've never pinned it down and watched it happen in
the debugger, is that when we see spurious newlines, it's because a
flush has taken place or the buffer has filled up. There is lots and
lots of flushing in the Perl test suite; you may just not have as
much flushing in what you're doing with bash.
In the bash change, I never flush, I just buffer the data in virtual
memory until someone reads it or there are no readers left with channels
on the mailbox. If I run out of virtual memory, then it will hang. So
far in all the scripts that I have run it since the change it has not
happened.
According to some comments in those Configure scripts, some versions of
the SED editor which are in common use have smaller limitations than I
have run into for virtual memory, so that is not a problem.
If I have to put in a flush algorithm, then I will need to store the
pipe data in a temporary file. That would be a bit messy at the
transition time from data that can be contained in virtual memory and to
the temp file usage.
I just found out an apparent undocumented feature of Perl exit()
handling on VMS that I did not implement. [.lib.pod.t]usage.t exposes it.
-John
[EMAIL PROTECTED]
Personal Opinion Only
