# Calling procedure from included .mod file, without explicit \`use\` statement

**URL:** <https://fortran-lang.discourse.group/t/calling-procedure-from-included-mod-file-without-explicit-use-statement/4535>\
**Category:** Help\
**Created:** [October 15, 2022, 7:51am UTC](https://fortran-lang.discourse.group/t/calling-procedure-from-included-mod-file-without-explicit-use-statement/4535 "2022-10-15T07:51:26Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ivanpribec](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ivanpribec/32/3290_2.png) [@ivanpribec](https://fortran-lang.discourse.group/u/ivanpribec)\
**Post date:** [October 15, 2022, 8:05am UTC](https://fortran-lang.discourse.group/t/calling-procedure-from-included-mod-file-without-explicit-use-statement/4535/2 "2022-10-15T08:05:37Z")

</div>

Take a look at this answer:

> [@What does implicit none (type,external) do?](https://fortran-lang.discourse.group/t/what-does-implicit-none-type-external-do/497/5):
>
> For reference, I’ll answer the subject question. implicit none (type,external) is a Fortran 2018 feature. implicit none(type) is the same as implicit none, disabling all implicit typing. implicit none(external) requires that any procedures referenced either have an explicit interface or be declared EXTERNAL. You can combine the options. Compilers supporting this may have a command line option to imply implicit none (external) in the same manner as options to disable implicit typing.

I’m guessing your module could have just picked up the procedure from the library and used it as an (implicit) external procedure. It does seem a bit weird though, as module procedures have their names mangled.

---

_[View the full topic](https://fortran-lang.discourse.group/t/calling-procedure-from-included-mod-file-without-explicit-use-statement/4535)._