Yes, please do. I don't plan on reviewing datetime in detail because I don't know much about the more complex use cases for it (the stuff that makes the design nontrivial), but I'd like to look at the public API in a way that makes the forest easily visible through the trees and see whether the simple things that I would use it for are sufficiently simple.<br>
<br><div class="gmail_quote">On Sat, Oct 9, 2010 at 8:15 PM, Andrei Alexandrescu <span dir="ltr"><<a href="mailto:andrei@erdani.com">andrei@erdani.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I suggest you generate html documentation and attach it. I can put it on my website.<br><font color="#888888">
<br>
Andrei</font><div><div></div><div class="h5"><br>
<br>
On 10/8/10 19:01 CDT, Jonathan M Davis wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I should probably add that the seven modules aren't exactly equal in size. In<br>
particular datetime.all only has its module documentation and public imports for<br>
all of the other modules, and datetime.other is quite small. I didn't<br>
necessarily split the code into modules in the best manner. I split it more on<br>
concepts than the amount of code in them (so datetime.timepoint probably has<br>
close to half of the code in it). I'm open to suggestions if someone has a<br>
better way to split the code up. Ideally, it would all be in one module, but it<br>
was too much for one.<br>
<br>
Also, as much as there is, a large portion of it is unit tests and<br>
documentation. There's definitely more unit tests than normal code, and there<br>
might be more documentation than normal code.<br>
<br>
One point that may need to be improved is the module documentation so that it's<br>
more obvious exactly what you need to just get the time and print it out or<br>
whatever the insanely simple operations are that would be typical in your<br>
average program that does little with the time. I am afraid that it is a bit<br>
like std.algorithm in that it's quite easy to use but a bit overwhelming to look<br>
at so that you _think_ that it's hard to use, even though it really isn't. I do<br>
have quite a few examples it the code though, and I hope that the documentation<br>
is generally clear enough. I tried to make it so that it was, but it really<br>
needs to have people who aren't familiar with it judge it at this point.<br>
<br>
- Jonathan M Davis<br>
_______________________________________________<br>
phobos mailing list<br>
<a href="mailto:phobos@puremagic.com" target="_blank">phobos@puremagic.com</a><br>
<a href="http://lists.puremagic.com/mailman/listinfo/phobos" target="_blank">http://lists.puremagic.com/mailman/listinfo/phobos</a><br>
</blockquote>
_______________________________________________<br>
phobos mailing list<br>
<a href="mailto:phobos@puremagic.com" target="_blank">phobos@puremagic.com</a><br>
<a href="http://lists.puremagic.com/mailman/listinfo/phobos" target="_blank">http://lists.puremagic.com/mailman/listinfo/phobos</a><br>
</div></div></blockquote></div><br>