# Call callback-function inside Behaviour-Module

**URL:** <https://forum.elixirforum.com/t/call-callback-function-inside-behaviour-module/67469>\
**Category:** Questions\
**Tags:** behaviours, callbacks\
**Created:** [November 13, 2024, 2:45pm UTC](https://forum.elixirforum.com/t/call-callback-function-inside-behaviour-module/67469 "2024-11-13T14:45:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dimitarvp](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/dimitarvp/32/38664_2.png) [@dimitarvp](https://forum.elixirforum.com/u/dimitarvp)\
**Post date:** [November 13, 2024, 3:09pm UTC](https://forum.elixirforum.com/t/call-callback-function-inside-behaviour-module/67469/3 "2024-11-13T15:09:45Z")

</div>

I would give you a thumbs up during code review on a PR like this – it’s all good.

If you are worried about this approach then the only other practice that’s more “micro” would be to only pass function references – but then you would be losing the compiler warnings if a contract is violated i.e. if the function has the same arity but accepts different kinds of arguments.

So IMO callback modules are the right solution here.

---

_[View the full topic](https://forum.elixirforum.com/t/call-callback-function-inside-behaviour-module/67469)._