<br><br><div class="gmail_quote">On Sun, May 16, 2010 at 06:13, Graham Fawcett <span dir="ltr"><<a href="mailto:fawcett@uwindsor.ca">fawcett@uwindsor.ca</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;">
<br>
'trunk/dranges' would be fine -- keeping 'trunk' makes good sense for<br>
a Subversion project. For my purposes, any depth is okay, e.g.<br>
'trunk/src/lang/d2/dranges' would also work. The key is that modules<br>
which belong to the 'dranges' package should exist in a 'dranges'<br>
directory.<br></blockquote><div><br>OK. I admit switching to a package.module naming convention quite recently (a month or so), so it's still a bit incomplete. <br>I should have done that.<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
What I'm doing is adding the parent of the 'dranges' directory to<br>
dmd's include-path. Then I just let DMD look up the module files using<br>
its own conventions (e.g. DMD expects that a module named foo.bar.baz<br>
will be defined in a file named foo/bar/baz.d). That's why I renamed<br>
trunk to dranges: it was the easiest way to honour the DMD naming<br>
convention.<br><br></blockquote><div><br>OK, got it. I'll add a dranges directory inside trunk today. And add a dranges dir in the downloadable .zip.That'a another alternative you have: look inside /download if there is something to get.<br>
<br>I'm following your project with interest, as that'd be cool to have an easy-to-use tool to grap projects. I use dstats from time to time and just dumped the files into my own project file, but a command-line tool is better.<br>
<br>Philippe<br><br></div></div>