At present, fpm is not enforcing this (we did at one point in the original Haskell version I think), but we do highly encourage it. Strictly enforcing it was going to be an impediment to adoption, so we decided not to.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
|
Module naming restrictions for fpm
|
42 | 1295 | November 13, 2022 | |
| Why do we need TYPEOF? | 72 | 1279 | April 3, 2025 | |
| Legacy Code Modernization: global common, equivalence out; modules, namelists in? | 37 | 1038 | May 12, 2024 | |
| The same named entity from different modules and/or program units cannot be referenced: bug? | 4 | 640 | February 16, 2024 | |
| Why I can access private module variable in this program? | 44 | 1932 | February 2, 2023 |