www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - std.stream and std.stdio

reply biozic <dransic free.fr> writes:
Is there a plan to deprecate part of (or all of) std.stream in favor of 
new Range-implemented streams as in std.stdio? A confusing point is that 
the documentation says nothing about the redundancy of std.stdio.File 
and std.stream.File. Another one is that stdin/out/err aren't Streams. 
Also, in a recent thread, a promising byLine-readable socket IO 
implementations was favored instead of std.socketstream.

Thanks,
Nicolas.
Apr 07 2010
parent "Lars T. Kyllingstad" <public kyllingen.NOSPAMnet> writes:
biozic wrote:
 Is there a plan to deprecate part of (or all of) std.stream in favor of 
 new Range-implemented streams as in std.stdio? A confusing point is that 
 the documentation says nothing about the redundancy of std.stdio.File 
 and std.stream.File. Another one is that stdin/out/err aren't Streams. 
 Also, in a recent thread, a promising byLine-readable socket IO 
 implementations was favored instead of std.socketstream.
 
 Thanks,
 Nicolas.

I believe std.stream is scheduled for deprecation in the not-too-distant future, so new code should use std.stdio.File. I also find the socket IO implementation to which you are referring (Adam Ruppe's, right?) very promising. I hope it is adopted into Phobos. After having used std.stdio.File for a while now, I've really come to like its interface. I hope Andrei succeeds in uniting streams and ranges. -Lars
Apr 07 2010