# Warning about variable conflict from module export?

**URL:** <https://discourse.julialang.org/t/warning-about-variable-conflict-from-module-export/119841>\
**Category:** New to Julia\
**Tags:** module\
**Created:** [September 25, 2024, 1:45am UTC](https://discourse.julialang.org/t/warning-about-variable-conflict-from-module-export/119841 "2024-09-25T01:45:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [September 25, 2024, 2:05am UTC](https://discourse.julialang.org/t/warning-about-variable-conflict-from-module-export/119841/2 "2024-09-25T02:05:26Z")

</div>

> [@aaoo](#):
>
> This may not work in v"1.10", got a warning on name conflicts.

That’s because you’re redefining the module and including it a second time, after already having used one of the imports from the first time.

This happens even if you do manual exports, i.e. if you paste the following code into the REPL twice:

```julia
module Foo; export x; x = 1; end
using .Foo
x

```

If you want to develop a module, the best thing to do is to put it into a package ([Best practise: organising code in Julia - #2 by stevengj](https://discourse.julialang.org/t/best-practise-organising-code-in-julia/74362/2)) and use Revise.jl.

PS. I moved this to new topic because your question has nothing to with the original thread. In general, be cautious about “necroposting” — posting new questions on threads that were resolved years ago.

---

_[View the full topic](https://discourse.julialang.org/t/warning-about-variable-conflict-from-module-export/119841)._