# How to make standard Julia package with input/options parameters in non compiled Julia files

**URL:** https://discourse.julialang.org/t/how-to-make-standard-julia-package-with-input-options-parameters-in-non-compiled-julia-files/60549
**Category:** Package Management
**Created:** [May 4, 2021, 10:33pm UTC](https://discourse.julialang.org/t/how-to-make-standard-julia-package-with-input-options-parameters-in-non-compiled-julia-files/60549 "2021-05-04T22:33:45Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![JosephPollacco](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/josephpollacco/32/51404_2.png) [@JosephPollacco](https://discourse.julialang.org/u/JosephPollacco)
#### Post date: [May 5, 2021, 3:03am UTC](https://discourse.julialang.org/t/how-to-make-standard-julia-package-with-input-options-parameters-in-non-compiled-julia-files/60549/3 "2021-05-05T03:03:58Z")

</div>

> [@lmiq](#):
>
> Usually those options would be out in a structure, which may be set by the user and passed to the functions.

Thanks for conforming that when a function is compiled into a Package  
it cannot read Julia files as input. As recommended, I will put the _Options_ into a `structure` and read the parameters from a separate input file which will be object of another topic [Discourse](https://discourse.julialang.org/t/what-recommended-format-of-input-parameters-options-of-a-large-hydrological-model-compiled-as-a-julia-package/60561)

---

_[View the full topic](https://discourse.julialang.org/t/how-to-make-standard-julia-package-with-input-options-parameters-in-non-compiled-julia-files/60549)._
