Stefano Zaghi
Stefano Zaghi
Hi Chris, great project, my best compliments! I would like to contribute if you like. In the past I have developed a generic container (based on an unlimited polymorphic class)...
Allow the definition of default value for **optional** dummy arguments: ```fortran subroutine foo(bar, baz=.false.) ! inline default value definition integer, intent(inout) :: bar logical, intent(in), optional :: baz if (baz)...
From a note on another thread... > avoid dead code, do not write code that has no effect Is this an agreed guideline? The discussion is open :smile: # Summary...
I feel that there is an almost unanimous agreement on that `implicit none` must be mandatory, but I guess many of you will provide interesting _exceptions_, so > do you...
For readability/debugging/robustness/safeness (what else?) purposes it could be interesting to add a guideline about > use keyword argument calling-style for all optional arguments in procedures callings e.g. ``` fortran subroutine...
Just a list (with no special order) of sources for inspiring us > feel free to correct/expand it - [Fortran 2003 standard](http://www.j3-fortran.org/doc/year/04/04-007.pdf) - [Modern Fortran: Style and Usage](http://www.amazon.com/Modern-Fortran-Norman-S-Clerman/dp/052173052X) - [The...
Be standard?
Dear all, I start with my first question for you, with the hope you are interested to discuss on. In my _best practices_ I always considered the _standard compliance_ as...
This is probably one of the most personal guideline. I have to admit that I have not yet found yhe one that I love so I often change my mind...
EDIT by @zbeekman: This thread is now locked. Please see #8 for a discussion on how to treat Fortran software/project licensing in this document, and #9 to discuss how to...
Dear all, as anticipated on Gitter, I have just created this repo with the purpose to collect the _best_ of our (your) Fortran practices. I think (and also @zbeekman does,...