Just wrote a command-line tool that imported a module with the "same name"
– except that the script had a name of the form foo, while the module was
named Foo.jl; when I tried running the script (which happened to be in my
Julia path, as I was in the same directory), it froze. If I renamed it, it
was OK. I'm guessing my "using Foo" statement somehow managed to end up
importing foo? I'm in OS X, where this sort of thing is a bit tricky; it
*pretends* to be case-sensitive, but in some cases it's really not. Still …
the missing .jl should have made a difference, no? (And also … should a
module importing itself really lead to an infinite loop? Wouldn't some kind
of error be better? Or perhaps even treat it like multiple/cyclic imports
in general, and simply ignore it?)
