[phobos] next release (module useability)

Jonathan M Davis jmdavisProg at gmx.com
Tue Sep 14 19:30:36 PDT 2010


On Tuesday 14 September 2010 18:21:37 Walter Bright wrote:
>  stdio is for buffered file I/O, file is for encapsulated file ops.

I confess that I see no point in separating code based on that, but regardless, 
the module names don't imply that their separation has anything to do with 
buffered I/O or encapsulated file ops. My first reaction from looking at the names 
is that std.stdio would be for console ops only and std.file would be for file 
ops. And since file I/O is still I/O, it would make sense for it to be in a 
module named std.stdio. Also, it seems to me that std.stdio is awfully small for 
a single module. So, combining them makes a lot of sense to me.

In any case, I don't think that the reason for the separation between std.stdio 
and std.file is at all obvious or that it ultimately makes much sense, and I'd 
love to see them combined. But obviously, it's not up to me.

- Jonathan M Davis


More information about the phobos mailing list