User Tools

Site Tools


dev:todo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
dev:todo [2015/06/15 14:33]
oschuett
dev:todo [2015/07/02 18:17]
oschuett
Line 7: Line 7:
   * Refactor ''​cp_output_handling.F''​ such that it does not require the input_section. Instead there should be a routine to parse the input section once and store that information into a novel ''​printkey_type''​.   * Refactor ''​cp_output_handling.F''​ such that it does not require the input_section. Instead there should be a routine to parse the input section once and store that information into a novel ''​printkey_type''​.
   * Evolve the printkey into a real logging mechanism. If the ''​WRITE''​ statements were converted into functions calls, one could annotate the output in a standardized way. Such annotations would then allow for parsing the output in a generic fashion.   * Evolve the printkey into a real logging mechanism. If the ''​WRITE''​ statements were converted into functions calls, one could annotate the output in a standardized way. Such annotations would then allow for parsing the output in a generic fashion.
-  * Remove the ''​required''​ flag from input keywords and sections. The flag states that there is no default value available, but the same effect can be achieved by simply not supplying a default value. To fully remove the flag one also has to adopt the generation of the input reference manual. 
   * Remove the ''​cp_error_type''​ and the '​pseudo exception handling'​ code like ''​IF (.NOT.failure)''​. These constructs clutter the code without providing any useful functionality. The side-feature of the error_type to carry a reference to a ''​cp_logger_type''​ is sparsely used. It can be completely replaced by the ''​add/​rm_default_logger''​ mechanism.   * Remove the ''​cp_error_type''​ and the '​pseudo exception handling'​ code like ''​IF (.NOT.failure)''​. These constructs clutter the code without providing any useful functionality. The side-feature of the error_type to carry a reference to a ''​cp_logger_type''​ is sparsely used. It can be completely replaced by the ''​add/​rm_default_logger''​ mechanism.
  
dev/todo.txt ยท Last modified: 2017/02/10 10:34 by oschuett