The problem is that some Julia processing stores references to definitions
in hidden locations which are not updated consistently, so you get
inconsistency like this:
julia> f(x)=x^2
f (generic function with 1 method)
julia> map(f,[1,2,3])
3-element Array{Int64,1}:
1
4
9
julia> f(x)=x^2+1
WARNING: Method definition f(Any) in module Main at REPL[7]:1 overwritten
at REPL[9]:1.
f (generic function with 1 method)
julia> [f(x) for x in [1,2,3]]
3-element Array{Int64,1}:
1
4
9
julia> for x in [1,2,3]; println(f(x)); end
2
5
10
julia> map(f,[1,2,3])
3-element Array{Int64,1}:
1
4
9
(Thanks to fcard for pointing this out. See this issue
<https://github.com/JuliaLang/julia/issues/18725> for more discussion.)
Fixing this and related problems is hard, but there is hope for v0.6.
Anyway, my point was that "function files" are more dangerous than "module
files", and that's why they generate more warnings.
In the REPL one can also drop *all* old definitions & bindings by using
workspace(), but I find that more painful than just using modules and
restarting Julia when
necessary.
If you're convinced that all this doesn't apply to your case, you can
suppress messages:
https://github.com/cstjean/ClobberingReload.jl#silencing-warnings
On Saturday, October 8, 2016 at 9:35:10 AM UTC-4, digxx wrote:
>
> Hey,
> Thx for ur answer. So The first time I call my program which includes a
> file with function definitions there is no problem. I do this because with
> 0.4 parallel loops didnt work with functions which are defined in the same
> file even though an @everywhere is prefixed.
> I still dont understand why this should happen at all. Isnt it totally
> natural that a function file where things like
> g(x)=x.^2
> are defined and not much more complex it might happen that I want to
> change it to
> g(x)=x.^2+1
> without restarting Julia in order to not get the error.
> This also happens in the REPL when I overwrite a simple function. So it is
> probably not correlated to the @everywhere.
> How can I avoid the warning or is it possible to "free" all allocated
> function definitions before I redefine them?
>
