[phobos] next release (module useability)
Andrei Alexandrescu
andrei at erdani.com
Tue Sep 14 09:19:03 PDT 2010
Answering to an older point:
On 9/11/10 0:40 CDT, SHOO wrote:
> My question is simpler.
>
> I want to know the reason.
>
> time is a concept including date.
> stopwatch/benchmark is a part of time, but it is not a part of date.
> date is redundant if so.
> Nonetheless what will the reason to add date to a module name be?
I think it's quite simple. First time I needed some time functions I
searched the library home page for "time". Couldn't find any. It took me
a while to find time-related functions inside std.date, and found the
connection tenuous. Probably it would be equally uneasy for others, too.
If there is only std.time it is presumable that somebody looking for
date functions would think of searching for "time".
But then "std.datetime" is 100% unambiguous. 10 people out of 10 would
know what it contains. And it's really no extra effort for us, so why not?
> /* The reason of this question is because there was the doubt why naming
> it is WAG for of the module of Phobos before in Japanese community. (The
> subject at that time was "Why are std.file and std.path separated?") */
It's a good point. The distinction between manipulating file names and
file contents is valid, but academic. For scripts, you'd need to import
both files most of the time anyway. What does WAG mean?
I think consolidating std.path and std.file into std.file would mark
progress.
Andrei
More information about the phobos
mailing list