# A native way to pass script arguments to include() **URL:** \ **Category:** Internals & Design\ **Tags:** proposal\ **Created:** [July 10, 2017, 3:56pm UTC](https://discourse.julialang.org/t/a-native-way-to-pass-script-arguments-to-include/4766 "2017-07-10T15:56:34Z")\ **Posts on this page:** 3\ **Page:** 1

**Author:** ![ephemeris](https://avatars.discourse-cdn.com/v4/letter/e/a9adbd/32.png) [@ephemeris](https://discourse.julialang.org/u/ephemeris)\ **Post date:** [July 10, 2017, 3:56pm UTC](https://discourse.julialang.org/t/a-native-way-to-pass-script-arguments-to-include/4766/1 "2017-07-10T15:56:34Z")

There is [that question on StackOverflow](https://stackoverflow.com/questions/44967240/juliapassing-argument-to-the-includefile-jl). I was wondering if passing arguments as a Collection to `include` function is against some ideas behind julia. Because if not, I think it could be a useful feature. As of now you are either required to modify your script with the suggested `isdefined()` check or redefine `ARGS` explicitly which results in a warning. I think It would be nice as it would for example streamline using others’ scripts that are not written as modules from within your own ones. ---

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ihnorton/32/26_2.png) [@ihnorton](https://discourse.julialang.org/u/ihnorton)\ **Post date:** [July 10, 2017, 4:00pm UTC](https://discourse.julialang.org/t/a-native-way-to-pass-script-arguments-to-include/4766/2 "2017-07-10T16:00:31Z")

2 posts were merged into an existing topic: [How to pass command line arguments to include(“”)?](https://discourse.julialang.org/t/how-to-pass-command-line-arguments-to-include-julia-file/4731) ---