On Tuesday, September 14, 2010 11:11:16 David Simcha wrote: > Funny, I was going to suggest just lumping all three (path, file, stdio).
Well, looking at the docs for std.stdio, it does some quite odd that it and std.file are separate. It seems quite natural to import one module for console I/O and another for file I/O, but given that the console I/O is essentially using file I/O to do its thing, it becomes quite odd for them to be separate. So, consolidating std.stdio and std.file starts looking like a good idea. And while I'd prefer that std.path stay separate, if std.stdio and std.file are a single module and that module is pretty much always used if std.path is used, then having it separate becomes useful pretty much only because it keeps the docs separate and thus less cluttered. So, there is some merit in combining all three. Certainly, looking at the API for std.stdio, I'd say that it definitely should be combined with std.file. - Jonathan M Davis _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
