# Tips to cope with scoping rules of top level \`for\` loops etc

**URL:** <https://discourse.julialang.org/t/tips-to-cope-with-scoping-rules-of-top-level-for-loops-etc/24902>\
**Category:** General Usage\
**Tags:** scope\
**Created:** [June 4, 2019, 12:17am UTC](https://discourse.julialang.org/t/tips-to-cope-with-scoping-rules-of-top-level-for-loops-etc/24902 "2019-06-04T00:17:55Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [June 5, 2019, 8:55pm UTC](https://discourse.julialang.org/t/tips-to-cope-with-scoping-rules-of-top-level-for-loops-etc/24902/11 "2019-06-05T20:55:34Z")

</div>

> [@stevengj](#):
>
> explaining the concept of scoping in the middle of a math lecture is impractical

Sure, and I get that. It’s kinda like how stopping to explain the concept of `IJulia.SOFTSCOPE[] = false` gets in the way of teaching what I actually want to teach. 😉

> [@stevengj](#):
>
> even if it comes with no benefit for serious software development that doesn’t use global scope much?

That’s unfair — there _are_ benefits to the 1.0 rules. It makes it obvious to both humans and static analyzers which identifiers are global. Heck, [the Rebugger depends upon it](https://discourse.julialang.org/t/another-possible-solution-to-the-global-scope-debacle/15894/196).

---

_[View the full topic](https://discourse.julialang.org/t/tips-to-cope-with-scoping-rules-of-top-level-for-loops-etc/24902)._