I'm not sure I follow, because the toy example I'm asking about does in fact use hierarchical module names...<div><br></div><div>are you proposing that a reasonable workaround in my use case is to do</div><div>:cd ..</div>
<div>:r<br>this seems like a reasonableish approach, or was there a different example you had in mind?<br><div class="gmail_quote">On Sun, Jul 18, 2010 at 1:34 PM, Anthony Cowley <span dir="ltr"><<a href="mailto:acowley@seas.upenn.edu">acowley@seas.upenn.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Sun, Jul 18, 2010 at 3:59 AM, Carter Schonwald<br>
<<a href="mailto:carter.schonwald@gmail.com">carter.schonwald@gmail.com</a>> wrote:<br>
> I don't think that semantics creates the sort of ambiguity that Kevin is<br>
> concerned about, and while yes there simple alternative approaches, they<br>
> require whatever is starting up ghci to know what the correct directory to<br>
> pass to the -i flag, and that seems a bit of a heavy weight expectation<br>
<br>
</div><div class="im">I usually use ghci's :cd command in this situation, and wouldn't want<br>
to think about changing source files depending on where they were on<br>
disk.<br>
<br>
While having to use fully hierarchical names might seem verbose, I<br>
have found it to be a very predictable mechanism that makes managing<br>
large-ish projects easier.<br>
<br>
Anthony<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br></div>