# Use of eval in closed module and "incremental compilation may be broken"

**URL:** <https://discourse.julialang.org/t/use-of-eval-in-closed-module-and-incremental-compilation-may-be-broken/30028>\
**Category:** General Usage\
**Created:** [October 17, 2019, 3:01pm UTC](https://discourse.julialang.org/t/use-of-eval-in-closed-module-and-incremental-compilation-may-be-broken/30028 "2019-10-17T15:01:05Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![tlienart](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tlienart/32/7640_2.png) [@tlienart](https://discourse.julialang.org/u/tlienart)\
**Post date:** [October 18, 2019, 5:09pm UTC](https://discourse.julialang.org/t/use-of-eval-in-closed-module-and-incremental-compilation-may-be-broken/30028/6 "2019-10-18T17:09:44Z")

</div>

So if anyone should read this question in the future, I finally found out that the problem was to specify properly where the `eval` happens (and yes you actually have to use `eval` here because the emitted code has to be from A not B)

Anyway so calling `parentmodule(T).eval` solves the problem, it took me some time to find it but it works perfectly for my use case 😅

---

_[View the full topic](https://discourse.julialang.org/t/use-of-eval-in-closed-module-and-incremental-compilation-may-be-broken/30028)._
