10 ms·
In early versions, DOS pipes weren't real pipes. It would run the first command and save the output to a temporary file; then once that was finished, run the s
by LukeShu 10y ago
In early versions, DOS pipes weren't real pipes. It would run the first command and save the output to a temporary file; then once that was finished, run the second command with the file as input. I'm not sure when it gained real pipes.
- flukus 10y agoAround windows nt/95 when multi-tasking was added would be my bet.
- pjc50 10y agoWindows pipes appear to still be second-class citizens. Look at this mess: http://stackoverflow.com/questions/34504970/non-blocking-read-on-os-pipe-on-windows?noredirect=1&lq=1 http://stackoverflow.com/questions/34504970/non-blocking-rea... The eventual solution using SetNamedPipeHandleState isn't really supported: https://msdn.microsoft.com/en-us/library/windows/desktop/aa365787(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/aa3... "Note that nonblocking mode is supported for compatibility with Microsoft LAN Manager version 2.0 and should not be used to achieve asynchronous input and output (I/O) with named pipes."