Fortran-FOSS-Programmers Best_Practices issues - Githubissues

Fortran-FOSS-Programmers / Best_Practices

the opinionated *best practices* of Fortran FOSS Programmers group

Creative Commons Attribution Share Alike 4.0 International

64 stars 10 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Highlighting Fortran codes

#18 han190 opened 4 years ago
1
Kind parameters

#17 raullaasner opened 6 years ago
8
Added examples and content, clarified language, and fixed typos.

#16 apthorpe closed 6 years ago
2
goto, is to be or not (used)?

#15 szaghi closed 5 years ago
64
Use keyword argument calling-style for all optional arguments in procedures callings

#14 szaghi opened 8 years ago
0
do we avoid dead code?

#13 szaghi opened 8 years ago
6
What constitutes idiomatic Fortran?

#12 rouson opened 8 years ago
12
On `use different styles concurrently`

#11 muellermichel opened 8 years ago
9
Is *explicit* better than implicit?

#10 szaghi opened 8 years ago
66
Select a license for *THIS DOCUMENT* and one for any code snippets included

#9 zbeekman opened 8 years ago
10
Fortran software project licensing considerations

#8 zbeekman opened 8 years ago
13
Select a license

#7 szaghi opened 8 years ago
23
Programmatically check/enforce "agreed upon" style and conventions

#6 zbeekman opened 8 years ago
7
Naming Conventions, which one?

#5 szaghi opened 8 years ago
53
Style guide for Fortran-FOSS group projects

#4 milancurcic closed 8 years ago
2
Sources of inspiration

#3 szaghi opened 8 years ago
9
Be standard?

#2 szaghi opened 8 years ago
37
Are you interested?

#1 szaghi opened 8 years ago
17