Reading input from piped stdin.

[Thomas]

On Friday, 14 February 2014 at 19:08:20 UTC, Adam D. Ruppe wrote:
> Just a quick look, but I betcha it has to do with buffering. 
> After writing the line to the pipe, call the flush() method on 
> the output pipe and see what happens there.
>
> (Pipes buffer differently than regular output so this is a 
> common mixup, especially with IDEs which communicate with 
> stdout via pipes normally!)
>
> let me know if it works

Impressive reply speed! :)

However calling pipes.stdin.flush() immediately after writeln did
not seem to work.