3

Screenshot / Code Snippet

Not yet available.

About

So far, in commit #2, can successfully parse the statistics API into an object. I'll update more as I get more of the API done (but for now, I need to go take a bike ride and enjoy the outdoors a bit).

License

Available under the MIT license.

Download

Development branches available on Launchpad. I was going to put it on Github, since I know many more SO users use that -- but I was having some SSH issues that I didn't want to take the time to resolve.

Platform

It should run anywhere that D 1.0 with Tango can be compiled.

Contact

Just me (Mark Rushakoff) (so far!). Contact me through Launchpad if necessary, or post/comment here.

Code

Written in D 1.0 with Tango, hoping to have no other dependencies. Code available on Launchpad as mentioned before. Check out the first part of the API that's been finished yet (Statistics.d) for a look at how elegant D's mixins can be.

Contributions certainly welcome, submit through Launchpad.

Improve this question
9
  • Just checked out the code... will compile it shortly. – Nathan Osman May 30 '10 at 2:28
  • @George: It's hardly in a usable state yet :( I'm just working through parsing different API calls into classes so far. Hopefully by the end of the long weekend, it will be something more usable. – Mark Rushakoff May 30 '10 at 3:03
  • @Mark: Ya, it won't compile :( – Nathan Osman May 30 '10 at 3:43
  • @George: I'm not sure how familiar you are with D -- are you set up to use Tango? If you're on Linux, these 3 bash scripts are the easiest way to switch back and forth between Phobos and Tango. If you are set up to use Tango, it should compile fine, although it won't do too much yet. – Mark Rushakoff May 30 '10 at 10:01
  • @Mark: I've never used it before in my life :) I just installed gdc and the tango headers. Some of the .d files compile, some don't. It would be great if this came with a makefile - then I could tell you exactly what goes wrong. – Nathan Osman May 30 '10 at 16:14
  • @George: If you run the included build.sh (which looks for dmd -- change as necessary), you should see only the line Unit tests passed. Let me know what it says, if it isn't that. As for why I don't have a Makefile yet, that's a two-part answer. 1. I don't know exactly how this library will be consumed. Right now, it can be simply dropped in to an existing project and compiled with everything else. 2. I don't know what the standard D build setup is -- I don't think Makefiles are idiomatic D. – Mark Rushakoff May 30 '10 at 16:32
  • The message I get is "No command 'dmd' found." What exactly is dmd? – Nathan Osman May 31 '10 at 1:24
  • @George: dmd is the Digital Mars D compiler. GDC should be equivalent, but I think it installs something like run-dmd.sh as a wrapper to translate the dmd arguments to GDC syntax. Even so, all that's going on in build.sh is compiling all *.d files with -unittest specified, then running the executable to verify the unit tests. The other option in the latest build is to do dmd -debug=statistics -run statistics.d which will download, parse, and print out information from /stats. – Mark Rushakoff May 31 '10 at 3:07
  • @Mark: Ah, okay. That makes sense. – Nathan Osman May 31 '10 at 5:08

You must log in to answer this question.

Browse other questions tagged .