Coding good practices: Difference between revisions

From The Yambo Project
Jump to navigation Jump to search
(Created page with "thumb|Coding good practices Some reasonable good practices are strongly suggested in order to reduce the possibilities of clashes with other parallel developments: ** Be modular. All branches except tech-XXX and phys-XXX can potentially limit the coding to modules. ** Do not repeat code. Being modular and releasing modules with examples reduce the chances to repeat code.")
 
No edit summary
 
Line 3: Line 3:
Some reasonable good practices are strongly suggested in order to reduce the possibilities of clashes with other parallel developments:
Some reasonable good practices are strongly suggested in order to reduce the possibilities of clashes with other parallel developments:


** Be modular. All branches except tech-XXX and phys-XXX can potentially limit the coding to modules.
* Be modular. All branches except tech-XXX and phys-XXX can potentially limit the coding to modules.
** Do not repeat code. Being modular and releasing modules with examples reduce the chances to repeat code.
* Do not repeat code. Being modular and releasing modules with examples reduce the chances to repeat code.

Latest revision as of 14:57, 2 February 2023

Coding good practices

Some reasonable good practices are strongly suggested in order to reduce the possibilities of clashes with other parallel developments:

  • Be modular. All branches except tech-XXX and phys-XXX can potentially limit the coding to modules.
  • Do not repeat code. Being modular and releasing modules with examples reduce the chances to repeat code.