deprecating std.stream, std.cstream, std.socketstream
Jonathan M Davis
jmdavisProg at gmx.com
Sun May 13 15:00:47 PDT 2012
On Sunday, May 13, 2012 14:38:23 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 think that it's been a foregone conclusion for some time that they were
going to go. We just haven't done it, because we don't have replacements for
them yet. IIRC Steven's std.stdio rewrite at least partially covers that, but
he hasn't been able to finish it yet.
- Jonathan M Davis
More information about the Digitalmars-d
mailing list