On Mon, Jul 15, 2013 at 9:55 AM, Peter Alexander <span dir="ltr">&lt;<a href="mailto:peter.alexander.au@gmail.com" target="_blank">peter.alexander.au@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Monday, 15 July 2013 at 15:45:47 UTC, Timothee Cour wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
---- src/foo/bar.d:<br>
// infers &#39;module foo.bar;&#39; instead of &#39;module bar;&#39;<br>
void barfun(){}<br>
----<br>
<br>
---- src/main.d:<br>
import foo.bar;<br>
void main(){}<br>
----<br>
<br>
dmd -Isrc src/main.d<br>
</blockquote>
<br></div>
And what if I compile it like this?<br>
<br>
dmd -c src/foo/bar.d<br>
dmd -c -Isrc src/main.d<br>
// link later<br>
<br>
I don&#39;t think this can work in general.<br>
</blockquote></div><div><br></div>Yes I thought about that case. It would still work by passing the same -I flags:<br><div>dmd -c -Isrc src/foo/bar.d</div><div>dmd -c -Isrc src/main.d<br>// link later<br></div><div><br></div>
<div>When a file would be fully specified on the command line as above, the -I flag would specify the offset from which to compute the relative path. I think it&#39;s a simple rule that makes code more DRY and easy to refactor.</div>