# Another possible solution to the global scope debacle

**URL:** https://discourse.julialang.org/t/another-possible-solution-to-the-global-scope-debacle/15894
**Category:** Internals & Design
**Created:** [October 4, 2018, 6:14pm UTC](https://discourse.julialang.org/t/another-possible-solution-to-the-global-scope-debacle/15894 "2018-10-04T18:14:07Z")
**Posts on this page:** 1
**Showing post:** 43

<div class="post-metadata">

### Author: ![JeffreySarnoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeffreysarnoff/32/1980_2.png) [@JeffreySarnoff](https://discourse.julialang.org/u/JeffreySarnoff)
#### Post date: [October 4, 2018, 10:34pm UTC](https://discourse.julialang.org/t/another-possible-solution-to-the-global-scope-debacle/15894/43 "2018-10-04T22:34:13Z")

</div>

```julia
module Module
    const CONST = 1 # not exported
end

using Module
# CONST is not global here, right?
# only Module.CONST would get at it, right?

```

---

_[View the full topic](https://discourse.julialang.org/t/another-possible-solution-to-the-global-scope-debacle/15894)._