Search results

Highlighting Fortran codes

Status: Open.

#18 In Fortran-FOSS-Programmers/Best_Practices;

· han190 opened on Jan 7, 2020

Kind parameters

Status: Open.

#17 In Fortran-FOSS-Programmers/Best_Practices;

· raullaasner opened on Jan 12, 2018

Use keyword argument calling-style for all optional arguments in procedures callings

Status: Open.

#14 In Fortran-FOSS-Programmers/Best_Practices;

· szaghi opened on Jan 21, 2016

do we avoid dead code?

question

Status: Open.

#13 In Fortran-FOSS-Programmers/Best_Practices;

· szaghi opened on Jan 21, 2016

What constitutes idiomatic Fortran?

question

Status: Open.

#12 In Fortran-FOSS-Programmers/Best_Practices;

· rouson opened on Jan 21, 2016

On use different styles concurrently

Status: Open.

#11 In Fortran-FOSS-Programmers/Best_Practices;

· muellermichel opened on Jan 21, 2016

Is *explicit* better than implicit?

question

Status: Open.

#10 In Fortran-FOSS-Programmers/Best_Practices;

· szaghi opened on Jan 18, 2016

Select a license for *THIS DOCUMENT* and one for any code snippets included

help wanted

question

Status: Open.

#9 In Fortran-FOSS-Programmers/Best_Practices;

· zbeekman opened on Jan 17, 2016

Fortran software project licensing considerations

help wanted

question

Status: Open.

#8 In Fortran-FOSS-Programmers/Best_Practices;

· zbeekman opened on Jan 17, 2016

Select a license

Status: Open.

#7 In Fortran-FOSS-Programmers/Best_Practices;

· szaghi opened on Jan 16, 2016

Programmatically check/enforce "agreed upon" style and conventions

Status: Open.

#6 In Fortran-FOSS-Programmers/Best_Practices;

· zbeekman opened on Jan 12, 2016

Naming Conventions, which one?

question

Status: Open.

#5 In Fortran-FOSS-Programmers/Best_Practices;

· szaghi opened on Jan 12, 2016