# Getting Line Error on stack trace when "using" modules

**URL:** <https://forum.elixirforum.com/t/getting-line-error-on-stack-trace-when-using-modules/10667>\
**Category:** Questions\
**Tags:** errors, tracing, stack\
**Created:** [December 7, 2017, 1:20am UTC](https://forum.elixirforum.com/t/getting-line-error-on-stack-trace-when-using-modules/10667 "2017-12-07T01:20:08Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![amnu3387](https://forum.elixirforum.com/letter_avatar_proxy/v4/letter/a/ed8c4c/32.png) [@amnu3387](https://forum.elixirforum.com/u/amnu3387)\
**Post date:** [December 7, 2017, 9:57pm UTC](https://forum.elixirforum.com/t/getting-line-error-on-stack-trace-when-using-modules/10667/9 "2017-12-07T21:57:45Z")

</div>

Besides my mental model when projecting this (and having to change function calls in so many places), nothing is wrong with calling functions where they’re located in the source code - I tend to do that usually ah. `alias` still implies calling the module name, and `import` I think I tried but then I would need to “import” things in multiple places - like in the sample, I would need to import “utils” & “legal” & “payment” and then in “payment” and “legal” probably import “utils” again, and so on, otherwise they would break.

Perhaps it’s just bad architecture 🙂 but given that I’m creating it as I go and don’t have the whole engine yet designed/thought about…

Thanks for your patience and suggestions. I will give this some thought (to break it up in the future) - and for now just add the trace

---

_[View the full topic](https://forum.elixirforum.com/t/getting-line-error-on-stack-trace-when-using-modules/10667)._