Turns out that the same code was being loaded; the issue was that the error
was in compilation, not execution (another victim of the tupocalypse), so
the debug statements weren't even given a chance to print anything.
On Sunday, April 19, 2015 at 5:04:00 PM UTC-7, Seth wrote:
>
> Hi,
>
> I have two julia binaries: one in /usr/local/bin (5-day-old master), and
> one in /Users/seth/dev/julia/julia/usr/bin/julia (this is the latest master
> from today). I'm seeing some very weird behavior: when I do a
> Pkg.dir("LightGraphs") in both, I get "/Users/seth/.julia/v0.4/LightGraphs
> ", but when I use a function in the package, different code is being
> executed.
>
> Things that may be significant:
>
> /Users/seth/.julia/v0.4/LightGraphs is a symlink to
> /Users/seth/dev/julia/wip/LightGraphs
>
> The code I'm executing is a separate module within LightGraphs ("module
> AStar") and the function (a_star) is exported:
>
> module AStar
>
>
> using LightGraphs
> using Base.Collections
> using Compat
>
> export a_star
> ...
>
> I changed a_star to print some debugging information (using both info()
> and println()). In the 5-day-old master REPL (/usr/local/bin), the
> debugging info is displayed when I invoke a_star(). In the new master
> REPL (/Users/seth/julia/julia/usr/bin), the debugging info is not printed,
> nor are any changes I make to astar.jl reflected when exiting and
> restarting the REPL and then issuing "using LightGraphs".
>
> This is probably a very simple mistake on my part but I'm too close to it.
> Could someone please point out what I'm doing wrong?
>
>
>
