# Variable scope concept

**URL:** <https://discourse.julialang.org/t/variable-scope-concept/122277>\
**Category:** General Usage\
**Tags:** scope\
**Created:** [November 5, 2024, 9:53am UTC](https://discourse.julialang.org/t/variable-scope-concept/122277 "2024-11-05T09:53:52Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![Benny](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Benny](https://discourse.julialang.org/u/Benny)\
**Post date:** [November 16, 2024, 5:54am UTC](https://discourse.julialang.org/t/variable-scope-concept/122277/22 "2024-11-16T05:54:57Z")

</div>

Julia’s VSCode extension lets you do equivalents of both `include`ing a file (source behavior) or pasting select lines into a REPL (interactive behavior), just choose what you need.

---

<div class="post-metadata">

**Author:** ![carstenbauer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/carstenbauer/32/4981_2.png) [@carstenbauer](https://discourse.julialang.org/u/carstenbauer)\
**Post date:** [November 16, 2024, 1:03pm UTC](https://discourse.julialang.org/t/variable-scope-concept/122277/23 "2024-11-16T13:03:31Z")

</div>

> [@hack3rcon](#):
>
> I’m a newbie and it’s really hard for me to understand what you said. In my opinion, such behavior is not acceptable. To write big projects, you need an IDE, and such behavior makes the programmer wrong.

The one thing you should take away from this thread, especially for big projects, is: Put your code in functions. In this case, there’s nothing to worry about. It will work the same way everywhere.

[Previous page](https://discourse.julialang.org/t/variable-scope-concept/122277.md?page=1)
