# Evaluation into closed module - what's wrong?

**URL:** https://discourse.julialang.org/t/evaluation-into-closed-module-whats-wrong/114526
**Category:** General Usage
**Tags:** metaprogramming, eval
**Created:** [May 21, 2024, 6:45pm UTC](https://discourse.julialang.org/t/evaluation-into-closed-module-whats-wrong/114526 "2024-05-21T18:45:56Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![gdalle](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/gdalle/32/27854_2.png) [@gdalle](https://discourse.julialang.org/u/gdalle)
#### Post date: [May 22, 2024, 5:05am UTC](https://discourse.julialang.org/t/evaluation-into-closed-module-whats-wrong/114526/4 "2024-05-22T05:05:26Z")

</div>

> [@mkitti](#):
>
> Rather you are calling a function during the extension’s init which calls `@eval` within SCT.

Within which module should i call `@eval` then? `Base`/`SpecialFunctions`?

It doesn’t seem possible to `@eval` into the calling scope itself 🤔

> [@Evaluation in calling scope?](https://discourse.julialang.org/t/evaluation-in-calling-scope/34897/2):
>
> There are probably workarounds to achieve what you want to achieve but the straight-forward answer is just that you cannot eval in calling scope since eval evaluates in global scope.

---

_[View the full topic](https://discourse.julialang.org/t/evaluation-into-closed-module-whats-wrong/114526)._