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
Copy file name to clipboardExpand all lines: STYLE_GUIDE.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@
11
11
12
12
## File naming conventions
13
13
14
-
- Source files should contain at most one `program` or `module`/`submodule`.
14
+
- Source files should contain at most one `program`, `module`, or `submodule`.
15
15
- The filename should match the program or module name and have the file extension `.f90` or `.F90` if preprocessing is required.
16
16
- If the interface and implementation is split using submodules the implementation submodule file should have the same name as the interface (parent) module but end in `_implementation`. E.g., `string_class.f90` and `string_class_implementation.f90`
17
17
- Tests should be added in the `tests` subdirectory and have the same name as the module they are testing with the `test_` prefix added. E.g., `string_class.f90` and `tests/test_string_class.f90`
0 commit comments