deprecating std.stream, std.cstream, std.socketstream

Robert Clipsham robert at octarineparrot.com
Sun May 13 17:38:01 PDT 2012


On 13/05/2012 22:38, Walter Bright wrote:
> This discussion started in the thread "Getting the const-correctness of
> Object sorted once and for all", but it deserved its own thread.
>
> These modules suffer from the following problems:
>
> 1. poor documentation, dearth of examples & rationale
>
> 2. toHash(), toString(), etc., all need to be const pure nothrow, but
> it's turning out to be problematic for doing it for these classes
>
> 3. overlapping functionality with std.stdio
>
> 4. they should present a range interface, not a streaming one

I make use of std.stream quite a lot... It's horrible, it has to go.

I'm not too bothered if replacements aren't available straight away, as 
it doesn't take much to drop 10 lines of replacement in for the 
functionality I use from it until the actual replacement appears.

-- 
Robert
http://octarineparrot.com/


More information about the Digitalmars-d mailing list