Changes between Version 29 and Version 30 of HowTo/FortranStandards

Timestamp:

2013-05-22T11:12:01+02:00 (11 years ago)

Author:

mmcgrath

Comment:

--

HowTo/FortranStandards

@@ -138 +138 @@
 [[BR]] 
 
-(1) '''Names of counters:''' Limit to four characters.  If the variable being looped over begins with "n", replace the "n" by an "i" for the counter name.  For example, nvm -> ivm, npts -> ipts, nelements -> iele.  Need to choose between kjpindex and npts!
+(1) '''Names of counters:''' Limit to four characters.  If the variable being looped over begins with "n", replace the "n" by an "i" for the counter name.  For example, nvm -> ivm, npts -> ipts, nelements -> iele.  
+
+Variables which have the same meaning but are named differently throughout the code: kjpindex/npts
 
 ----
@@ -188 +190 @@
 [[BR]] 
 
+= Code structure =
+
+Do we add more folders to handle parts of the code which are not neatly classified by the existing folders (e.g., effective LAI), or do we put everything in one folder and just impose naming conventions on all file names (e.g., stomate_*f90, sechiba*f90, which are already somewhat done)? 
+
+[[BR]] 
+
+
+= Points to Discuss (as recommended by Philippe) =
+
+(1) Use of structures to group related variables
+
+(2) Long argument lists, structures, or "shared modules" to exchange variables between routines?
+> MJM: I like long argument lists or structures, since then it is easier to see what is modified by the routine
+
+
+[[BR]] 
 
 = Signatories =