You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking through the grid implementation (which looks great!), I noticed most of use statements do not have only,so just pointing to the module. By explicitly specifying public entities (subroutine, function or variables etc.) with only, it is easier to tell where the entities are coming from, and easier to trace the code, and also allow to avoid name conflict (can rename referred entities. As the codes get complex, this helps maintainability, code documentation without comments.
Hi @SnowHydrology and @GreyEvenson-NOAA,
Looking through the grid implementation (which looks great!), I noticed most of
use
statements do not haveonly
,so just pointing to the module. By explicitly specifying public entities (subroutine, function or variables etc.) withonly
, it is easier to tell where the entities are coming from, and easier to trace the code, and also allow to avoid name conflict (can rename referred entities. As the codes get complex, this helps maintainability, code documentation without comments.something to think about...
https://stackoverflow.com/questions/51686745/why-should-i-use-use-only-in-fortran
The text was updated successfully, but these errors were encountered: