Commit 407736e

committed

docs: STYLE GUIDE attribute ordering convention

1 parent 79c9bf2 commit 407736eCopy full SHA for 407736e

File tree

-10

lines changed

-10

lines changed

Lines changed: 9 additions & 10 deletions

Original file line number	Diff line number	Diff line change
`@@ -61,16 +61,15 @@ focus on the semantics of the proposed changes rather than style and formatting.`
`61`	`61`	```
`62`	`62`	When defining many arrays of the same dimension, `dimension` can be used as an exception if it makes the code less verbose.
`63`	`63`	* If the `optional` attribute is used to declare a dummy argument, it should follow the `intent` attribute.
`64`		-* For module procedures, declare attributes before the `module` keyword for better retro compatibility:
`65`		`- Use this:`
`66`		- ```
`67`		`- <attribute> <attribute> module <function/subroutine> <name>`
`68`		- ```
`69`		`- instead of:`
`70`		- ```
`71`		`- module <attribute> <attribute> <function/subroutine> <name>`
`72`		- ```
`73`		`-`
	`64`	`+* For module procedures, it is recommended to declare attributes before the module keyword for better retro compatibility (Projects using CMake versions lower than CMake 3.25.0 are concerned see Spurious modules).`
	`65`	`+Prefere the following pattern:`
	`66`	+```
	`67`	`+<attribute> <attribute> module <function/subroutine> <name>`
	`68`	+```
	`69`	`+instead of:`
	`70`	+```
	`71`	`+module <attribute> <attribute> <function/subroutine> <name>`
	`72`	+```
`74`	`73`	`## End <scope> block closing statements`
`75`	`74`
`76`	`75`	`Fortran allows certain block constructs or scopes to include the name of the program unit in the end statement.`

Comments

(0)