This is a long-standing issue. See https://github.com/JuliaLang/julia/issues/265
Den fredagen den 7:e mars 2014 kl. 17:17:49 UTC+1 skrev David Moon: > > In Julia-0.3.0-prerelease-d2d9bd93ed.app on Mac OS X 10.6: > > julia> p() = q() > p (generic function with 1 method) > julia> p2() = q() > p2 (generic function with 1 method) > julia> q() = 1 > q (generic function with 1 method) > julia> q() > 1 > julia> p() > 1 > julia> q() = 2 > q (generic function with 1 method) > julia> q() > 2 > julia> p2() > 2 > julia> p() > 1 # !!! > > Geeze Louse! p is still calling the old version of q! No wonder I am > having trouble debugging anything. I thought I was losing my mind when > changes to a previously defined method sometimes did not have the expected > effect. > > Shouldn't defining a method decache anything that has inlined the same or > a less specific method for that function? > > Would I get better results by using an IDE rather than a plain vanilla > read-eval-print loop? Which IDE? >
