Style convention

[lmdiazangulo]

Here we try to establish some conventions. Feel free to propose your own!

1. All names and comments must be in English.
2. Fortran keywords always lowercase. Example: type rather than TYPE.
3. No space with parenthesis when declaring variables. Example: write type(edge_t) rather than type (edge_t).
4. Fortran type names should end with _t. Example: prefer type(cell_t) rather than type(cell).
5. Fortran module names should end with _m. Example: prefer module mesh_m rather than module mesh.
6. Prefer endings in two words. Example: prefer end if rather than endif.
7. Do not use Fortran keywords as variable names. Example: do not use size as variable name.
8. No space between ( and the interior of functions or during variable declaration. Example prefer integer(kind rather than integer ( kind
9. All parameters must be named with upper cased letters. Example: prefer RKIND to rkind.

[adrianarce-elemwave]

What about function, subroutine and variable naming?

Even though fortran does not discern between lower and upper cases I suggest the following convention:

• Subroutine and functions snake-case (Eg. function_with_name)
• Variables with camel case for easy reading on IDE (Eg. variableWithComplexName)

[lmdiazangulo]

What about function, subroutine and variable naming?

Even though fortran does not discern between lower and upper cases I suggest the following convention:

• Subroutine and functions snake-case (Eg. function_with_name)
• Variables with camel case for easy reading on IDE (Eg. variableWithComplexName)

Why differentiate between function names and variable names? Is there a specific reason for that?

[adrianarce-elemwave]

It may be useful to discern them as functions then to be defined in other modules. User will notice those calls easier and not try to find them at subroutine/function header. This problem is more common between functions and variables as both can be assigned ('=') whereas subroutines can be discerned by the 'call' keyword.

[Alberto-o]

If anything, for me it'd make more sense the opposite convention.

• Functions describe processes, and their names might be quite long. CamelCase takes less space.
• Variables describe objetcst or states, and their names are usally shorter, so it's ok if snake_case takes a bit longer.

I see I have been applying this convention, but I don't have a strong opinion.

[lmdiazangulo]

I think I am more leaned towards cameCalse for functions and snake_case for variables.