At 11:17 AM 9/5/2000 -0700, Peter Prymmer wrote:
>So now that the deadline pressure is off, would anyone object to making
>vmspipe a little more optional rather than a required part of the build?
I wouldn't really object in theory, but I think this would be a bit tricky
-- not to mention ugly -- in practice. Essentially one would have to use
the patch as a guide and put ifdefs around hundreds of lines of code in
vms.c to separate the new way from the old way. Then you'd have to decide
what to do with openpid.t, since it hangs under the old dispensation. There
are probably other things I am forgetting.
It seems to me worth noting that the extra lines in the test output, though
they certainly look bad, don't appear to cause the tests to fail. Could
there not just be something quirky about a subprocess talking to another
subprocess talking to a parent process whose output is a terminal device and
whose messaging is turned off? I still think we shoudl fix it if we can
nail down what's causing it, but I'm not convinced that you're better off
without the piping mods just because the test output looks flaky.
FWIW, I built 5.7.0 on a 7.1 AXP system using DEC C 5.2 and did *not*
encounter the spurious linefeeds.
_______________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
